新しいBoxサポートサイトへようこそ。 変更点の詳細はこちらをご確認ください .

Pull latest events using stream_position or created_after, created_before

新規投稿

コメント

3件のコメント

  • kendomen

    We use stream_position and store events in azure data warehouse.   We then take out duplicates using event_id's because azure data warehouse allows for duplicate event_id's.

     

    I believe there's always a little bit of duplicates using stream_position so if you're using a database, you can just make your event_id a key and it should work fine.

    0
    コメントアクション パーマリンク
  • schindhi12

    Thanks for reply.

    So starting the stream_position directly (say 12356) during the next run until i read all entities/events would give me new set of events recently created? 

    We will get duplicate events only on User events but not on Admin events. Correct ?

     

    I see in documentation, When you request user events, Box delivers a low-latency, highly reliable list of all events related to the user's account. Because of its emphasis on returning complete results quickly, Box may return duplicate events, and events may delivered out of order.


    0
    コメントアクション パーマリンク
  • kendomen

    I've only worked with admin events and I do get duplicates on those.

    0
    コメントアクション パーマリンク

サインインしてコメントを残してください。