search

k2v-academy / K2View-Academy

Other
0 stars 0 forks source link

Behavior of Reference Tables #1056

Closed GRFJiFXOBptf1n1NiYK7E9No0rMCGH4sQgUAFZ9 closed 6 months ago

GRFJiFXOBptf1n1NiYK7E9No0rMCGH4sQgUAFZ9 commented 6 months ago

Hi,

We are doing Reference Syncs using ref_Sync tables='all'; One of the ref table failed because of some issue in the source and the fabric node was restarted. The ref_Status for that table is showing as READY. image However in the k2_jobs table it is showing up as FAILED. image When a Batch tries to run on an LU that uses this Reference table it does not proceed forward and it fails while checking the status of this ref table.

Is this the correct behavior of the ref table, showing as READY after the restart even though the last sync failed ? How can we make sure that the table sync was successful?

Thank you.

i7QC2njzxHCc0LYBqCh0HQf30xF2DYuJjqtFbNe commented 6 months ago

Hi,

This is a bug, we plan to resolve it on next Fabric release (8.1), better to track it on freshdesk.

GRFJiFXOBptf1n1NiYK7E9No0rMCGH4sQgUAFZ9 commented 6 months ago

Hi Lion,

Thank you for your response. Is the batch process checking the k2jobs table before starting and not the ref_Status? Which tables should we check to confirm that the ref table loads have been completed successfully?

Regard, Debargha