.net client on github


(medcl-2) #1

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Shay Banon) #2

Hey,

Looks good!. Just a few notes on the client (really applies to any client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in 0.11
    there will be an option for a thrift API (similar to HTTP, so simple to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java client
    as the languages are so similar. Of course, C# has burst ahead of Java over
    the past few years so cool things like dynamic aspects and such can be used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl medcl@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(medcl-2) #3

hi,shay banon,
thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in 0.11
    there will be an option for a thrift API (similar to HTTP, so simple to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java client
    as the languages are so similar. Of course, C# has burst ahead of Java over
    the past few years so cool things like dynamic aspects and such can be used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Shay Banon) #4

No, elasticsearch does not support Avro (yet). Avro is a pretty good
serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl medcl@163.com

hi,shay banon,
thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in 0.11
    there will be an option for a thrift API (similar to HTTP, so simple to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of Java
    over
    the past few years so cool things like dynamic aspects and such can be
    used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Martijn Laarman) #5

Hey Medcl,

I am also in the process of writing a .net client perhaps we should see if
we can make it a bundled effort instead? I do think the term
"ElasticSearch.NET" should be reserved for a propper .NET port of the whole
ElasticSearch code base.

-Martijn Laarman

2010/9/26 Shay Banon shay.banon@elasticsearch.com

No, elasticsearch does not support Avro (yet). Avro is a pretty good
serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl medcl@163.com

hi,shay banon,

thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in 0.11
    there will be an option for a thrift API (similar to HTTP, so simple to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of Java
    over
    the past few years so cool things like dynamic aspects and such can be
    used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Shay Banon) #6

Lately I really liked the work games around ES (like pyes for python), how
about NEST?

2010/9/27 Martijn Laarman m.laarman@datheon.com

Hey Medcl,

I am also in the process of writing a .net client perhaps we should see if
we can make it a bundled effort instead? I do think the term
"ElasticSearch.NET" should be reserved for a propper .NET port of the whole
ElasticSearch code base.

-Martijn Laarman

2010/9/26 Shay Banon shay.banon@elasticsearch.com

No, elasticsearch does not support Avro (yet). Avro is a pretty good

serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl medcl@163.com

hi,shay banon,

thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in 0.11
    there will be an option for a thrift API (similar to HTTP, so simple to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of Java
    over
    the past few years so cool things like dynamic aspects and such can be
    used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Shay Banon) #7

Ohh, and of course I am all for the idea of joining forces and building a
client, I think its a superb idea.

-shay.banon

p.s. of course, its word games, not work games, I am having a really bad
typing day, come over to the IIRC, me make many funnies....

2010/9/27 Shay Banon shay.banon@elasticsearch.com

Lately I really liked the work games around ES (like pyes for python), how
about NEST?

2010/9/27 Martijn Laarman m.laarman@datheon.com

Hey Medcl,

I am also in the process of writing a .net client perhaps we should see if
we can make it a bundled effort instead? I do think the term
"ElasticSearch.NET" should be reserved for a propper .NET port of the whole
ElasticSearch code base.

-Martijn Laarman

2010/9/26 Shay Banon shay.banon@elasticsearch.com

No, elasticsearch does not support Avro (yet). Avro is a pretty good

serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl medcl@163.com

hi,shay banon,

thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in
    0.11
    there will be an option for a thrift API (similar to HTTP, so simple
    to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of Java
    over
    the past few years so cool things like dynamic aspects and such can be
    used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Martijn Laarman) #8

I'm loving NEST so much i went ahead and created a repo for it :slight_smile:

Will move my .NET client from my private repo to there tonight after work.

2010/9/27 Shay Banon shay.banon@elasticsearch.com

Ohh, and of course I am all for the idea of joining forces and building a
client, I think its a superb idea.

-shay.banon

p.s. of course, its word games, not work games, I am having a really bad
typing day, come over to the IIRC, me make many funnies....

2010/9/27 Shay Banon shay.banon@elasticsearch.com

Lately I really liked the work games around ES (like pyes for python), how

about NEST?

2010/9/27 Martijn Laarman m.laarman@datheon.com

Hey Medcl,

I am also in the process of writing a .net client perhaps we should see
if we can make it a bundled effort instead? I do think the term
"ElasticSearch.NET" should be reserved for a propper .NET port of the whole
ElasticSearch code base.

-Martijn Laarman

2010/9/26 Shay Banon shay.banon@elasticsearch.com

No, elasticsearch does not support Avro (yet). Avro is a pretty good

serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl medcl@163.com

hi,shay banon,

thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in
    0.11
    there will be an option for a thrift API (similar to HTTP, so simple
    to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of
    Java over
    the past few years so cool things like dynamic aspects and such can
    be used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(Shay Banon) #9

One more thing about clients, if they there is momentum behind them, then I
can also open a repo (with proper permissions) under elasticsearch group (
github.com/elasticsearch). This might help in joining forces.

-shay.banon

2010/9/27 Martijn Laarman m.laarman@datheon.com

I'm loving NEST so much i went ahead and created a repo for it :slight_smile:

http://github.com/Mpdreamz/NEST

Will move my .NET client from my private repo to there tonight after work.

2010/9/27 Shay Banon shay.banon@elasticsearch.com

Ohh, and of course I am all for the idea of joining forces and building a
client, I think its a superb idea.

-shay.banon

p.s. of course, its word games, not work games, I am having a really bad
typing day, come over to the IIRC, me make many funnies....

2010/9/27 Shay Banon shay.banon@elasticsearch.com

Lately I really liked the work games around ES (like pyes for python), how

about NEST?

2010/9/27 Martijn Laarman m.laarman@datheon.com

Hey Medcl,

I am also in the process of writing a .net client perhaps we should see
if we can make it a bundled effort instead? I do think the term
"ElasticSearch.NET" should be reserved for a propper .NET port of the whole
ElasticSearch code base.

-Martijn Laarman

2010/9/26 Shay Banon shay.banon@elasticsearch.com

No, elasticsearch does not support Avro (yet). Avro is a pretty good

serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl medcl@163.com

hi,shay banon,

thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in
    0.11
    there will be an option for a thrift API (similar to HTTP, so simple
    to
    change) which is more performant.

  2. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of
    Java over
    the past few years so cool things like dynamic aspects and such can
    be used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(medcl-2) #10

NEST is really great,i am in, Martijn Laarman,we do it together.

On 9月27ζ—₯, δΈ‹εˆ10ζ—Ά03εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

One more thing about clients, if they there is momentum behind them, then I
can also open a repo (with proper permissions) under elasticsearch group (
github.com/elasticsearch). This might help in joining forces.

-shay.banon

2010/9/27 Martijn Laarman m.laar...@datheon.com

I'm loving NEST so much i went ahead and created a repo for it :slight_smile:

http://github.com/Mpdreamz/NEST

Will move my .NET client from my private repo to there tonight after work.

2010/9/27 Shay Banon shay.ba...@elasticsearch.com

Ohh, and of course I am all for the idea of joining forces and building a
client, I think its a superb idea.

-shay.banon

p.s. of course, its word games, not work games, I am having a really bad
typing day, come over to the IIRC, me make many funnies....

2010/9/27 Shay Banon shay.ba...@elasticsearch.com

Lately I really liked the work games around ES (like pyes for python), how

about NEST?

2010/9/27 Martijn Laarman m.laar...@datheon.com

Hey Medcl,

I am also in the process of writing a .net client perhaps we should see
if we can make it a bundled effort instead? I do think the term
"ElasticSearch.NET" should be reserved for a propper .NET port of the whole
ElasticSearch code base.

-Martijn Laarman

2010/9/26 Shay Banon shay.ba...@elasticsearch.com

No, elasticsearch does not support Avro (yet). Avro is a pretty good

serialization library (though the binary smile format for json I talked
about is just as good, and does not require mappings). On the other hand, it
does not (yet) have a good story for transport, so you need to write your
own transport for it. On the server side I can hack a TCP based transport
for avro quite easily, but it does require writing a TCP client for it on
the client side..., which is more complex than thrift, which already has a
transport story.

-shay.banon

2010/9/26 Medcl me...@163.com

hi,shay banon,

thanks for your notes,and dynamic object and linq in c# is cool,i'll
use them in the client,BTW does elasticsearch also support avro?

On 9月26ζ—₯, 上午6ζ—Ά14εˆ†, Shay Banon shay.ba...@elasticsearch.com wrote:

Hey,

Looks good!. Just a few notes on the client (really applies to any
client
developed on top of elasticsearch):

  1. The transport should be pluggable. It is HTTP currently, but in
    0.11
    there will be an option for a thrift API (similar to HTTP, so simple
    to
    change) which is more performant.
  1. The .NET client can try and follow similar concepts are the Java
    client
    as the languages are so similar. Of course, C# has burst ahead of
    Java over
    the past few years so cool things like dynamic aspects and such can
    be used
    to really make the user experience nice...

On Sat, Sep 25, 2010 at 6:30 AM, Medcl me...@163.com wrote:

Hey,
I'v wappered a .net client, on
http://github.com/medcl/ElasticSearch.Net,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.:slight_smile:


(system) #11