Yes, there will be an official client for .NET.
Our decision to create our own clients was mostly about consistency for our
users. To do that we created a set of low-level clients that map very
closely to the REST api. We made sure (and are continuously doing so) that
these clients implement all the API endpoints as well as all parameters and
to the right thing.
We tried our best to avoid any design decisions in those clients to make
sure everybody could use them, even if it means creating their own
abstraction on top of it. The overhead of the clients are so small and
their design flexible enough (we hope) that all the other clients can live
on top of these.
"the intention is to provide a solid base which can be used by other
implementors if they want to add specializations. we take care of the hard
stuff like node failover, while sticking very close to the standard ES REST
API". things like LINQ would be out of scope for this client, but eg the
NEST client could be implemented on top of the official .net client to
provide linq support while taking advantage of the networking improvments
I hope that answers your first question. For more information Honza Krai
will be doing a webinar about this - why we chose to do the clients, what
drove the design decisions we took. It should take place next week sometime.
On Thursday, October 24, 2013 5:58:38 AM UTC-5, joe castle wrote:
I still think that it would be nice to get an answer if there will be an
official .NET client. It has nothing to do with NEST being good or not
(it's not that all python clients were bad so they had to make an official
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 firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.