Hi, camel-twitter store the sinceId in memory, so if you restart the camel context, the id will be reset. I think we could add a new parameter on the sinceId to the twitter endpoint to resolve the issue.
So I just fill a JIRA[1] for it. [1]https://issues.apache.org/jira/browse/CAMEL-5937 Willem -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sunday, January 6, 2013 at 11:55 PM, matteo.redae...@gmail.com wrote: > Hello > > I'm testing camel-twitter component. I have shared my code at > > http://www.redaelli.org/matteo-blog/2012/12/29/apache-camel-how-to-collect-data-from-twitter/ > > I have question about filtering OLD tweets: if would like to create one > single endpoint/a service for twitter searches and retrieve the words to be > searched from a database > > In camel-twitter page I read > > filterOld: Filter out old tweets, that has previously been polled. This > state is stored in memory only, and based on last tweet id. > > QUESTION 1) is the state saved in memory related to the endpoint or the > query search? > > QUESTION 2) Is it possible to add new parameter sinceid to the camel-twitter > component? with other tool/languages I usually use and save the "sinceid" > value in order to retrieve the next time only the newest tweets... > It would also be useful when stopping and restarting my routes (I suppose > you loose the stat that is saved in memory) in order not to download what I > already downloaded ... > > Regards > Matteo > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/twitter-component-sinceid-parameter-tp5725013.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
