Forum Discussion

hmenco's avatar
hmenco
Frequent Visitor
5 years ago
Solved

Remove duplicates, keep the latest entry (Sharepoint as source)

Hi! I have here a FCONS table that has multiple Reservation No.

 

I only need the LATEST entry of the Reservation No. (highlighted in yellow)

 

I have resolved this before with Table.Buffer on my local folder as source. But since I have migrated the source to Sharepoint, I need to redevelop this again and noticed that Table.Buffer may not be applicable anymore since it slows down the performance.

 

Hoping someone could help me with a workaround, Or walk me through the Table.Buffer with Sharepoint as source.

 

EDIT: As much as possible, the most EFFICIENT way applicable to BIG DATA.

Thanks!

  • Hi! Thanks for taking time. I have resolved the issue by sorting descendingly the RunDate then partition by Reservation No. - add index column, expand the partition table and remove its duplicates.

7 Replies

  • hmenco's avatar
    hmenco
    Frequent Visitor

    Hi! Thanks for taking time. I have resolved the issue by sorting descendingly the RunDate then partition by Reservation No. - add index column, expand the partition table and remove its duplicates.

    • lbendlin's avatar
      lbendlin
      Super User

      ImkeF thank you for the warning. Since this is a SharePoint source I assume no query folding is happening and the sort is safe-ish?

      • ImkeF's avatar
        ImkeF
        Community Champion

        Hi lbendlin ,

        no, that's not how I understood the thread:
        .." or because when run locally it may constraint the operators in some ways that would make the operation inefficient or impossible to enforce.."
        To me this means that even locally evaluated queries won't have a guaranteed sort order.

         

  • There's a simple trick. Sort your data as needed (which is unfortunate as it is very costly) - in your case you need to sort by Rundate descending - and then select the {Reservation No.]  column and choose "Remove Duplicates".  That will only keep the first row for each Reservation No.  which is actually the last row due to the sorting etc.

    • hmenco's avatar
      hmenco
      Frequent Visitor

      I've done this but it doesn't keep the LATEST entry. Any other workaround? Thanks!

  • ImkeF I see.  So yes, the Group By approach makes more sense as long as that bug exists.  Performance will be horrible in both cases, I assume.