Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indexing support via native API #17

Closed
michaelklishin opened this issue Feb 16, 2013 · 3 comments
Closed

Indexing support via native API #17

michaelklishin opened this issue Feb 16, 2013 · 3 comments
Assignees
Labels

Comments

@michaelklishin
Copy link
Member

This is a pretty sizable task but I will use a single issue for it.

@ghost ghost assigned michaelklishin Feb 16, 2013
@davie
Copy link
Contributor

davie commented Feb 16, 2013

When you say native API do you mean using the ES transport client or node client rather than the rest API?(http://www.elasticsearch.org/guide/reference/java-api/client.html)

@michaelklishin
Copy link
Member Author

Transport/node/local clients, yes.

michaelklishin pushed a commit that referenced this issue Feb 17, 2013
… exists

Basic structure is already in place and it is now clear that we will be
able to provide an API that matches our REST API almost one to one.

There is currently a problem that will take some travis-ci.org CI env tweaks:

 * ES cluster name needs to be specified when connecting, so it has to be known
 * We assume it is set via ES_CLUSTER_NAME

References #17, #18.
@davie
Copy link
Contributor

davie commented Feb 18, 2013

Presumably the driver for this is performance? I'd be interested if you'd done any performance tests on this - I was hoping to move over to the rest API from the native client to avoid connection issues when ES versions don't match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants