I would like to get https://issues.apache.org/jira/browse/LUCENE-6527
in 5.2.1 too. It is quite a bad performance bug if you use a filtering
TermQuery as it will load norms for nothing.
On Mon, Jun 8, 2015 at 9:39 PM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
I can volunteer as RM
I've completed work on the cloud tab for the AngularJS UI. I'm now making final
checks and preparing a patch that I hope someone will commit for me :-)
Thanks!
Upayavira
On Tue, Jun 9, 2015, at 11:55 AM, Shalin Shekhar Mangar wrote:
Go ahead Adrien. I'll cut the RC when you're done.
On
Go ahead Adrien. I'll cut the RC when you're done.
On Tue, Jun 9, 2015 at 3:24 PM, Adrien Grand jpou...@gmail.com wrote:
I would like to get https://issues.apache.org/jira/browse/LUCENE-6527
in 5.2.1 too. It is quite a bad performance bug if you use a filtering
TermQuery as it will load norms
Thanks Steve!
On Tue, Jun 9, 2015 at 7:25 PM, Steve Rowe sar...@gmail.com wrote:
On Jun 9, 2015, at 8:57 AM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
Looks like there are several small fixes that need to be added. I'll cut
an RC tomorrow morning India time so that we have
Yeah, I’ll port that too.
On Tue, Jun 9, 2015 at 12:36 PM Karl Wright daddy...@gmail.com wrote:
There may be a prerequisite ticket fix that needs pulling up too?
r1683532 | dsmiley | 2015-06-04 08:32:45 -0400 (Thu, 04 Jun 2015) | 1 line
LUCENE-6520: Geo3D GeoPath.done() would throw an NPE
LUCENE-6535 is another one.
On Tue, Jun 9, 2015 at 10:57 AM Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
Thanks Steve!
On Tue, Jun 9, 2015 at 7:25 PM, Steve Rowe sar...@gmail.com wrote:
On Jun 9, 2015, at 8:57 AM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
Looks
There may be a prerequisite ticket fix that needs pulling up too?
r1683532 | dsmiley | 2015-06-04 08:32:45 -0400 (Thu, 04 Jun 2015) | 1 line
LUCENE-6520: Geo3D GeoPath.done() would throw an NPE if adjacent path
segments w
ere co-linear
Karl
On Tue, Jun 9, 2015 at 12:30 PM,
As mention in the JIRA ticket; this won’t be back-ported as it only applies
to the WGS84 feature added in 5.3. Sorry for any confusion.
On Tue, Jun 9, 2015 at 12:42 PM david.w.smi...@gmail.com
david.w.smi...@gmail.com wrote:
Yeah, I’ll port that too.
On Tue, Jun 9, 2015 at 12:36 PM Karl
I’m +1 to this. We can consider changing our mind once 5.3 is nocking on
the door if there are serious problems.
On Tue, Jun 9, 2015 at 2:36 PM Erick Erickson erickerick...@gmail.com
wrote:
Upayavira:
I'm a little reluctant to try to port the simpler patch to 5.2.1 as
this is all new
I'd say, let's get this release out - I'm happy with either patch
getting in. Then, let's see the flow of bug reports we get. That'll help
us understand how stable (or otherwise) it is, and thus whether we
should be shooting for 5.3 or 5.4.
Upayavira
On Tue, Jun 9, 2015, at 07:07 PM, Erick
Upayavira:
I'm a little reluctant to try to port the simpler patch to 5.2.1 as
this is all new functionality. I can be argued into it though.
It seems that the goal here is to get mileage out of the Angular JS
port before making it the default. What do you (and others) think
about changing 5.3
A user found a nasty DefaultSolrHighlighter performance bug with an easy
fix — https://issues.apache.org/jira/browse/SOLR-7655 I’m running tests
now.
On Tue, Jun 9, 2015 at 2:48 PM david.w.smi...@gmail.com
david.w.smi...@gmail.com wrote:
I’m +1 to this. We can consider changing our mind once
Looks like there are several small fixes that need to be added. I'll cut an
RC tomorrow morning India time so that we have enough time to back port
these items.
I'll also setup a local Jenkins build for 5.2
On 09-Jun-2015 6:10 pm, Erik Hatcher erik.hatc...@gmail.com wrote:
And here’s a fix
See https://issues.apache.org/jira/browse/SOLR-7638
Whilst I'd love to see the paging functionality in the cloud tab, I'd
suggest we leave that out of a point release, and just apply the SOLR-7638-
simple.patch file which makes three small, simple changes to get the
angular cloud tab back
And here’s a fix worth getting into 5.2.1 while we’re at it as well:
https://issues.apache.org/jira/browse/SOLR-7652
https://issues.apache.org/jira/browse/SOLR-7652
—
Erik Hatcher, Senior Solutions Architect
http://www.lucidworks.com http://www.lucidworks.com/
On Jun 8, 2015, at 3:15 PM,
I’ve gotten the two fixes (new admin Cloud UI and example/files
update-script.js) into 5_2 branch. Bring on the 5.2.1 RC!
—
Erik Hatcher, Senior Solutions Architect
http://www.lucidworks.com http://www.lucidworks.com/
On Jun 9, 2015, at 2:42 PM, Upayavira u...@odoko.co.uk wrote:
I'd
On Jun 9, 2015, at 8:57 AM, Shalin Shekhar Mangar shalinman...@gmail.com
wrote:
Looks like there are several small fixes that need to be added. I'll cut an
RC tomorrow morning India time so that we have enough time to back port these
items.
I'll also setup a local Jenkins build for
://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Monday, June 08, 2015 7:06 PM
To: dev@lucene.apache.org
Subject: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?
I broke it. SOLR-7588 fixes it. It hasn't been
, June 08, 2015 7:06 PM
To: dev@lucene.apache.org
Subject: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?
I broke it. SOLR-7588 fixes it. It hasn't been committed yet.
The dataimport section of the admin UI doesn't work because I
apparently put coffeescript into the admin
+1 for bug fix releases. Though I'd say we can wait for a couple of days
and give some time to others to fix other bugs that they'd want to get into
5.2.1, if there are any.
P.S.: Who's the RM? :-)
On Mon, Jun 8, 2015 at 10:06 AM, Shawn Heisey apa...@elyograg.org wrote:
I broke it. SOLR-7588
- without a lock.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Monday, June 08, 2015 7:06 PM
To: dev@lucene.apache.org
Subject: Looks like I broke Solr
: Monday, June 08, 2015 7:34 PM
To: dev@lucene.apache.org
Subject: RE: Looks like I broke Solr 5.2.0 - do we need a 5.2.1?
Hi,
If we do a bugfix relaese I would like to get the LUCENE-6482 (classloading
deadlock) in. This is not a new bug, but it is very nasty and affects
Elasticsearch. Solr
I can volunteer as RM unless someone else wants to.
On Tue, Jun 9, 2015 at 12:45 AM, Anshum Gupta ans...@anshumgupta.net
wrote:
+1 for bug fix releases. Though I'd say we can wait for a couple of days
and give some time to others to fix other bugs that they'd want to get into
5.2.1, if there
+1 for 5.2.1.
Steve
www.lucidworks.com
On Jun 8, 2015, at 1:06 PM, Shawn Heisey apa...@elyograg.org wrote:
I broke it. SOLR-7588 fixes it. It hasn't been committed yet.
The dataimport section of the admin UI doesn't work because I apparently
put coffeescript into the admin UI instead
I broke it. SOLR-7588 fixes it. It hasn't been committed yet.
The dataimport section of the admin UI doesn't work because I apparently
put coffeescript into the admin UI instead of javascript. Is this a bad
enough problem to warrant a bugfix release?
Thanks,
Shawn
25 matches
Mail list logo
