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.
Hey,
Looks good!. Just a few notes on the client (really applies to any client
developed on top of elasticsearch):
-
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. -
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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
I'm loving NEST so much i went ahead and created a repo for it 
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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 (
elasticsearch · GitHub). 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
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):
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.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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.
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 (
elasticsearch · GitHub). 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
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):
- 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.
- 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
GitHub - medcl/ElasticSearch.Net: a client written in .net, won‘t maintenance any more,
it now supports the basic features and i'll imporve it in future.
i hope you'll like it.