I have some difficulty getting started with the Elastic Search Ruby client.
Could you someone please point me to documentation or example
implementations. I am having difficulty from moving from Tire to ES ruby
client.
Does the ES ruby client have similar callbacks and that tire provides. Also
where can I learn the syntax of mappings like I use in Tire.
One of the problems I have with Tire is that it tries to connect to the ES
cluster each time I start the console, which slows the application down and
also cause connection issues if the some people in my group don't have
access to the ES cluster from various networks they use.
Does ES ruby client also try and connect to the cluster each time the
application starts?
If yes, is there a way to avoid that?
Also, in any case, is there a way to avoid Tire from connecting to the
cluster each time on startup.
Regarding the Ruby client; did you see the docs in the github repo?
On Thursday, November 14, 2013 8:22:22 AM UTC, Karan Verma wrote:
Hello
I have some difficulty getting started with the Elastic Search Ruby
client. Could you someone please point me to documentation or example
implementations. I am having difficulty from moving from Tire to ES ruby
client.
Does the ES ruby client have similar callbacks and that tire provides.
Also where can I learn the syntax of mappings like I use in Tire.
One of the problems I have with Tire is that it tries to connect to the ES
cluster each time I start the console, which slows the application down and
also cause connection issues if the some people in my group don't have
access to the ES cluster from various networks they use.
Does ES ruby client also try and connect to the cluster each time the
application starts?
If yes, is there a way to avoid that?
Also, in any case, is there a way to avoid Tire from connecting to the
cluster each time on startup.
There will be a suite of gems offering similar features of Tire soon,
namely the ActiveRecord/Model and Rails integration, automatic callbacks,
importing routines, etc.
One of the problems I have with Tire is that it tries to connect to the ES
cluster each time I start the console, which slows the application down and
also cause connection issues if the some people in my group don't have
access to the ES cluster from various networks they use.
Could you describe this issue in more detail, preferably at Github issues
for Tire? Tire indeed tries to connect to the cluster (to check whether it
should create an index for your model, etc), but this shouldn't result in
any "connection issues" or other errors.
Also, in any case, is there a way to avoid Tire from connecting to the
cluster each time on startup.
Again, unless you've discovered a bug this shouldn't be an issue.
When are the suite of Gems planned to be released? Regarding Tire
connecting to the cluster, it was not a bug. I want to understand why is it
necessary to check whether there's an index for the model. Can we avoid
this check?
I have some difficulty getting started with the Elastic Search Ruby
client. Could you someone please point me to documentation or example
implementations. I am having difficulty from moving from Tire to ES ruby
client.
you cannot, in fact "move" from Tire to the new Elasticsearch Ruby client ( GitHub - elastic/elasticsearch-ruby: Ruby integrations for Elasticsearch). Tire and the client
have quite different scopes and focus: the new client is focused on the low
layers such as transport, API calls, etc.
There will be a suite of gems offering similar features of Tire soon,
namely the ActiveRecord/Model and Rails integration, automatic callbacks,
importing routines, etc.
One of the problems I have with Tire is that it tries to connect to the
ES cluster each time I start the console, which slows the application down
and also cause connection issues if the some people in my group don't have
access to the ES cluster from various networks they use.
Could you describe this issue in more detail, preferably at Github issues
for Tire? Tire indeed tries to connect to the cluster (to check whether it
should create an index for your model, etc), but this shouldn't result in
any "connection issues" or other errors.
Also, in any case, is there a way to avoid Tire from connecting to the
cluster each time on startup.
Again, unless you've discovered a bug this shouldn't be an issue.
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.