Hi Adrien,
Good news! The problem is solved.
Can't wait for the release containing the fix, but for now I will use my
own build :)
On Thursday, February 6, 2014 5:25:11 PM UTC+1, Nils Dijk wrote:
Yay!
I will try this somewhere tomorrow. Thanks for fixing, much appreciated!
Seems like it
Excellent news, thanks for checking! RC2 was the last release candidate, so
the next release containing the fix should be 1.0 GA. Hopefully it will be
out soon.
On Fri, Feb 7, 2014 at 12:39 PM, Nils Dijk m...@thanod.nl wrote:
Hi Adrien,
Good news! The problem is solved.
Can't wait for the
Yay!
I will try this somewhere tomorrow. Thanks for fixing, much appreciated!
Seems like it was difficult to find. Since it only happens when a 'page'
gets recycled internally.
On Thursday, February 6, 2014 3:53:46 PM UTC+1, Adrien Grand wrote:
It took me some time but I finally managed to
Sorry, but your file at https://gist.github.com/8803745.git is broken, it
contains invalid JSON, so it can not be processed.
It would be helpful to provide a script with escaped JSON in bulk format.
From what I suspect, you do not use keyword analyzer for faceting/agg'ing,
so you will get all
Thanks. I tried to reproduce it on 1.0.0.RC2, but without success.
curl '0:9200/aggsbug/_mapping?pretty'
{
aggsbug : {
mappings : {
messages : {
properties : {
a : {
type : string,
analyzer : keyword
}
}
}
}
}
}
I just installed 1.7u25 on a mac with maverick to try to reproduce the
issue, but without success (on 1.0.0-RC2).
On Wed, Feb 5, 2014 at 4:49 PM, Nils Dijk m...@thanod.nl wrote:
Hi Adrien,
I'm using OSX (Mavericks) and java: (having the issue)
$ java -version
java version 1.7.0_25
Thanks for the effort.
I tried running on 1.7.0_51, and it gave me the same issue.
I was trying to find out if I could disable this unsafe string comparisons,
but could not really find where that should be disabled. Is there an easy
way for me to switch back that change? Do you know on what
On Wed, Feb 5, 2014 at 6:01 PM, Nils Dijk m...@thanod.nl wrote:
I was trying to find out if I could disable this unsafe
string comparisons, but could not really find where that should be
disabled. Is there an easy way for me to switch back that change? Do you
know on what commit this was
Ok, I was preparing to do a long bisecting session, but I started with the
commit you highlighted below (4271d573d60f39564c458e2d3fb7c14afb82d4d8) and
the commit before that one (6481a2fde858520988f2ce28c02a15be3fe108e4). And
as it turns out, it is the breaking commit.
If I build the commit of
Hi Jörg,
Glad you could reproduce with my updated gist.
cb.
On Wednesday, February 5, 2014 8:18:39 PM UTC+1, Jörg Prante wrote:
Nils, I ran the test on my Mac, and I can reproduce the issue. And also on
Linux.
Unfortunately the Mac locked up and I had to cold reboot, and my
copy/paste
I've loaded the same dataset in ES1.0.0.Beta2 with the same index
configuration as in the topic start.
However now the numbers are consistent if I call the same aggregation
multiple times in a row AND the number match the numbers of the facets.
This leads me to the conclusion something is
To follow up,
I have a contained test suite at https://gist.github.com/thanodnl/8803745for
this problem. It contains two files:
1. aggsbug.sh
2. aggsbug.json
The .json file contains ~1M documents newline separated to load into the
database, I was not able to create a curl request to
12 matches
Mail list logo
