[ 
https://issues.apache.org/jira/browse/CAMEL-27288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-27288:
--------------------------------
    Fix Version/s: 4.24.0

> camel-atom - with the default options the consumer skips new entries for 
> good: entries published before an edited entry, and entries with the same date
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-27288
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27288
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-atom
>            Reporter: shashank
>            Assignee: shashank
>            Priority: Major
>             Fix For: 4.24.0
>
>
> h3. What happens
> Since 4.21 the {{atom}} consumer is idempotent by default (CAMEL-23220) with 
> {{ItemUpdatedIdempotentStrategy}}, which skips an entry whose updated (or 
> published) date is not after the date of the entry routed before it. Without 
> {{sortEntries}} (the default) the entries are routed in the order of the feed 
> reader: the newest published first, routed from the end of the list. So:
> * An entry that was updated after newer entries were published (an edited 
> post) is routed first, and every newer entry with an earlier updated date is 
> skipped, in that poll and in all later ones. With 
> {{src/test/data/edited-feed.atom}} one poll routes 1 of the 4 entries.
> * An entry with the same date as the entry routed before it (several entries 
> published in the same second, or dates without a time) is skipped for good: 
> with three entries of the same date only one is routed.
> Nothing is logged above DEBUG. CAMEL-25549 fixed the order for 
> {{sortEntries=true}} only.
> h3. How to reproduce
> {{AtomEntryDefaultIdempotencyTest}} (camel-atom, file feeds, the consumer 
> polled directly twice) and 
> {{ItemUpdatedIdempotentStrategyTest.testEntriesWithEqualDateAndDifferentIds}}.
> h3. Fix
> With the default strategy the consumer routes the entries by their updated 
> date (as with {{sortEntries=true}}), and the strategy remembers the ids 
> ({{atom:id}}, else the link) of the entries routed with the latest date, so 
> another entry with that date is routed once and not again. 
> {{idempotent=false}} and other strategies keep the order of the feed.
> _Filed with Claude Code on behalf of allthingssecurity._



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to