?
Thanks
--Mahesh
On Saturday, July 5, 2014 8:46:59 AM UTC-7, kimchy wrote:
Heya, I worked a bit on it, and 1.x (upcoming 1.3) has some significant
perf improvements now for this case (including improvements Lucene wise,
that are for now in ES, but will be in Lucene next version). Those include
nodes (nested document scales out well, many fields don't).
On Tuesday, July 8, 2014 11:41:11 AM UTC+2, Maco Ma wrote:
Hi Kimchy,
I rerun the benchmark using ES1.3 with default settings (just disable the
_source _all ) and it makes a great progress on the performance. However
Solr still
Heya, I worked a bit on it, and 1.x (upcoming 1.3) has some significant
perf improvements now for this case (including improvements Lucene wise,
that are for now in ES, but will be in Lucene next version). Those include:
6648: https://github.com/elasticsearch/elasticsearch/pull/6648
6714:
I wonder why you are asking for this feature? If its because Java broke
backward comp. on serialization of InetAddress that we use in our
exceptions, then its a bug in Java serialization, hard for us to do
something about it.
You will loose a lot by trying to serialize exceptions using JSON,
are, then upgrade your JVM”
Especially in large SOA shops
This just decouples the Client and Server deployments.
Thanks much,
— Chris
On Mar 21, 2014, at 12:18 PM, kimchy kim...@gmail.com javascript:
wrote:
I wonder why you are asking for this feature? If its because Java broke
backward
