Thanks for showing interest in this idea. It is not yet generalized. But I
have a plan to generalize it. We can definitely start discussion on
elasticsearch-hadoop issues.
I will share my presentation after the HBase Conf so that you will have
better idea about this HBase Elasticsearch integration point.
Regards,
Dibyendu
On Friday, June 7, 2013 4:50:27 AM UTC-6, kimchy wrote:
this is great! would love to see if we can generalize it (if its not
already...) and integrate it to elasticsearch-Hadoop project!
if it is possible, lets start a dicussion on an issue on
elasticsearch-Hadoop project.
On Wed, Jun 5, 2013 at 9:57 PM, Dibyendu Bhattacharya < dibyendu.b...@gmail.com <javascript:>> wrote:
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Dibyendu, please consider making an abstraction for the indexer piece, so
people can plug other indexing engines, such as Solr(Cloud) in there. Oh,
I guess this assumes you will open-source this, but I'm not sure if you are
planning on doing that or not?
THANKS for your share, but i have a question.
how does it deal with the write failure when writed to hbase success but
failed in ES?
thanks.
在 2013年6月14日星期五UTC+8上午11时22分51秒,Dibyendu Bhattacharya写道:
Here is the ppt . HBase Conf will upload the video soon in their website.
Dibyendu
On Thursday, June 13, 2013 7:02:33 PM UTC-7, dancer wrote:
I have the same question as dancer.
How could I deal with failures in inserting data to ES or HBase. Retry or
RollBack?
As we all know, RollBack in HBase or ES dose not easily especially that
will happen in concurrent environment.
We hope to build secondaryindex and search on HBase with Elasticsearch, and
we are working on this.
Could you share your experience when ES cluster getting big? the problems /
bugs you encountered? is ES stable and high-performance in large-scale data?
On Thursday, June 6, 2013 3:57:53 AM UTC+8, Dibyendu Bhattacharya wrote:
We do Elasticsearch consulting all the time (see sig) and some of of
clients have multi-billion document indices with high index and/or query
rates.
It's stable and works well most of the time. Like anything else, it has its
quirks and requires some learning. We've seen our ES customers having
issues with split brain and there are a couple of oldish issues open where
others are reporting seeing the same. I imagine/hope ES is working on
fixing this.
We hope to build secondaryindex and search on HBase with Elasticsearch,
and we are working on this.
Could you share your experience when ES cluster getting big? the problems
/ bugs you encountered? is ES stable and high-performance in large-scale
data?
On Thursday, June 6, 2013 3:57:53 AM UTC+8, Dibyendu Bhattacharya wrote:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.