Forum Discussion
table refresh doesn't find changes but partition refresh does
- 1 year ago
Hi markmsc ,
Can you please share an update to your issue and let us know if you were able to resolve it by using azure pipeline-orchestrated XMLA refresh of the model, as this seems to be the best possible workaround currently available.
Sharing an update and accepting the reply which may have helped you in the direction will surely help other community memebers who may experience the same error in the future.
Thank you
Are you doing a "full" refresh on the table. If not then only active partitions will be touched. Make sure the partition in question is definitely in the active scope, also check the bookmark on the partition and make sure your more recent data has a different value, to ensure it is not being skipped
Hello Deku and thanks for replying.
The scheduled IR's are run by the service and I assume that is doing full, but I don't know since I don't think that is configurable. But if I refresh a table myself (using TE3), then yes, I am running a full. The partition in question is definitely in the active scope. Our active period is five days and the archive period is five days before that. The partition in question is "yesterday", so well within the active scope.
I'll double check the bookmarks on the partitions in question.
- Deku1 year agoSuper User
You can see the types of refresh here
In the service it likey uses automatic on the model. Refresh on tables and partitions are slightly different.
Sounds like it might be bookmark related. See the blog on polling expressions.
- markmsc1 year agoResolver I
Hello again Deku .
I took a look at the partition properties this morning before the first scheduled refresh. The bookmark date is before the updated date on the rows I would have expected to be dropped from the model by this first refresh. So at least from that angle, things seem to be in order.
However, you mentioned that the scheduled refresh runs an Automatic type. I saw in this article that Automatic will do things to a partition when it is in a state other than Ready. If in Ready, presumably the Automatic refresh does nothing. For the partition in question in my model, I saw today, prior to the scheduled refresh, that it is in Ready state. So I assume this is the issue: the refresh is skipping it because of its state.
I am trying to find information on what Ready means, and what might put a partition into some other state such that an automatic refresh would pay attention to it. I wondered if you have any pointers here.
Mark
- Deku1 year agoSuper User
If your force a refresh of the partition does the bookmark change?