I read that when you select Store Changes without applying them, the task does not use batch apply mode and therefore does not utilize the attrep_apply_changes table. This raises the question: how are changes processed and delivered to Databricks Delta when staging occurs via S3? Interestingly, even after choosing Store Changes, the configuration still shows Change Processing Tuning options set for batch apply mode, which seems contradictory.
In general store changes tables include all the changes that were captured by Replicate. Your observation is correct. i.e. the "Change Processing Tuning" option is grayed out only when apply changes & store changes are turned off. When ONLY stored changes is on (apply chages is off) none of the setting from the "Change Processing Tuning" option is relevant. I would suggest you open a case so that it will be passed to R&D as a product issue and they can fix it.
So, does this mean that in a task configured as Full Load + Store Changes, none of the Change Processing Tuning options apply? If that’s the case, and since these options are not grayed out, could this be considered a bug or an issue with Qlik as a tool?
By Change Processing Tuning, I’m referring specifically to Batch Tuning, Transaction Offload Tuning, and Miscellaneous Tuning. If I try to tweak any of these settings, are you saying there will be no actual impact in the background, and the change will only reflect in the UI without affecting processing behavior?
