Hej, I may be completely wrong, but this is IMHO not a good approach to sync data. A real solution for an Elasticsearch River would be a hook to the HBase Cluster Replication [1] and not by polling the dataset with select *... However that would be a lot more work, but would be a "real" push.
*Maybe* the river @ github could be made smarter once native HBase Timestamps are made in Phoenix somehow; as each cell in HBase is fully timestamped (and Phoenix doesn't mess with it, so it's always the last "UPSERT") this could be an approach. But in contrast to Cluster Replication this is still polling and will be slow on big datasets. [1] http://hbase.apache.org/book.html#cluster_replication Regards On Thu, Dec 18, 2014 at 6:51 AM, Subacini B <[email protected]> wrote: > > Hi, > > http://lessc0de.github.io/connecting_hbase_to_elasticsearch.html > > *curl -XPUT 'localhost:9200/_river/phoenix_jdbc_river/_meta' -d '{ "type" > : "jdbc", "jdbc" : { "url" : "jdbc:phoenix:localhost", "user" : "", > "password" : "", "sql" : "select * from test.orders" } }'* > > Followed the steps and i am able to successfully index the data to > Elasticsearch from Hbase.But if i do updates to records , the changes did > not reflect in ElasticSearch. Is it possible to automatically sync > updated/changed data? > > Thanks >
