Hi Ryan,
the whole thing was discussed quite often all around the world. We could use
the same logic we have for Javadocs and set the bootclasspath, but I don’t
think any developer will set this, because it makes configuring your build
environment complicated.
For Javadocs we have the
Hi Hoss,
this may easily overflow (not even Integer.compare may be implemented by
subtraction!!!). I committed a duplicate of the code from Lucene's
FieldComparator, which is correct.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
[
https://issues.apache.org/jira/browse/SOLR-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924790#comment-13924790
]
ASF subversion and git services commented on SOLR-5818:
---
Commit
I committed a fix. Maybe I should just scrub these mega-long terms
out of the big test line docs file ... but I sort of like that it's
there.
Mike McCandless
http://blog.mikemccandless.com
On Fri, Mar 7, 2014 at 11:07 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build:
Hi all,
Java 8 will get released (hopefully, but I trust the release plan!) on March
18, 2014. Because of this, lots of developers will move to Java 8, too. This
makes maintaining 3 versions for developing Lucene 4.x not easy anymore (unless
you have cool JAVA_HOME cmd launcher scriptsusing
On Fri, Mar 7, 2014 at 9:01 PM, Da Huang dhuang...@gmail.com wrote:
Hello, everyone,
My name is Da Huang. I'm studying for my master degree of Computer Science
in Peking University. I have been using lucene for about half a year. It's
so elegent that I hope to have a chance to contribute some
Sorry, but I disagree. We shouldn't release a new major version for
arbitrary reasons. Meanwhile the 4.x releases keep getting better, maybe it
could go to 4.12 or 4.15 before 4.x runs out of steam.
On Mar 8, 2014 6:27 AM, Uwe Schindler u...@thetaphi.de wrote:
Hi all,
Java 8 will get released
If they are lucene docids it is fine.
On Mar 8, 2014 6:11 AM, Uwe Schindler u...@thetaphi.de wrote:
Hi Hoss,
this may easily overflow (not even Integer.compare may be implemented by
subtraction!!!). I committed a duplicate of the code from Lucene's
FieldComparator, which is correct.
-
Hmmm, first warning you that all the nuances of different Java
versions really give me a headache...
I broke the build the same way a while ago, so now I issue the
command
export JAVA_HOME=`/usr/libexec/java_home -v 1.6`
before compiling any 4x branch.
So trying to compile this line:
if
But it is declared as long[] in the code, so either the declaration of the
array is wrong or the code overflows.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de/ http://www.thetaphi.de
eMail: u...@thetaphi.de
From: Robert Muir
Ok, then let’s release 4.8 using Java 7 as minimum requirement! Both is fine to
me. I just want Java 6 go away!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de/ http://www.thetaphi.de
eMail: u...@thetaphi.de
From: Robert Muir [mailto:rcm...@gmail.com]
+1, thats the right solution.
On Sat, Mar 8, 2014 at 8:18 AM, Uwe Schindler u...@thetaphi.de wrote:
Ok, then let’s release 4.8 using Java 7 as minimum requirement! Both is fine
to me. I just want Java 6 go away!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
[
https://issues.apache.org/jira/browse/SOLR-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924861#comment-13924861
]
Furkan KAMACI commented on SOLR-5762:
-
When I use a Solrj version greater than 4.5.1
There is no good reason for that packing of docid and position into a long.
the positions should be a separate array (SorterTemplate already being
used here to sort things in parallel)
On Sat, Mar 8, 2014 at 8:16 AM, Uwe Schindler u...@thetaphi.de wrote:
But it is declared as long[] in the
And let's also move trunk to Java 8 then.
My suggestion is either:
- Backport all Java 8 changes from trunk to 4.x (and reassign fix versions to
4.8)
- Or re-branch trunk to branch_4x, incorporating *all* changes from trunk (so
svn rm branch_4x; svn cp trunk branch_4x)
It depends on how much
On Sat, Mar 8, 2014 at 8:47 AM, Uwe Schindler u...@thetaphi.de wrote:
And let's also move trunk to Java 8 then.
My suggestion is either:
- Backport all Java 8 changes from trunk to 4.x (and reassign fix versions to
4.8)
Assuming you mean java7, +1 :)
- Or re-branch trunk to branch_4x,
And let's also move trunk to Java 8 then.
My suggestion is either:
- Backport all Java 8 changes from trunk to 4.x (and reassign fix versions to
4.8)
Of course, backport Java 7 changes . :-)
- Or re-branch trunk to branch_4x, incorporating *all* changes from trunk (so
svn rm branch_4x;
+1 that is the right thing to do. Let move forward Java 6 went EOL and
it's a security risk for all running it since security fixes are not
ported anymore afaik. We should just move on here to be honest!
simon
On Sat, Mar 8, 2014 at 2:18 PM, Uwe Schindler u...@thetaphi.de wrote:
Ok, then let’s
[
https://issues.apache.org/jira/browse/SOLR-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-5825:
-
Attachment: SOLR-5825.patch
Patch with unused SorlRequest removed and an entry in CHANGES.txt
[
https://issues.apache.org/jira/browse/LUCENE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924872#comment-13924872
]
ASF subversion and git services commented on LUCENE-5497:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-5497.
-
Resolution: Fixed
Fix Version/s: 5.0
4.8
hunspell doesnt handle
[
https://issues.apache.org/jira/browse/LUCENE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924873#comment-13924873
]
ASF subversion and git services commented on LUCENE-5497:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-5835.
---
Resolution: Not A Problem
The Overseer will batch state updates without limit.
[
https://issues.apache.org/jira/browse/SOLR-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924887#comment-13924887
]
Mark Miller commented on SOLR-5835:
---
Ah, you are right - we already are breaking it up. I
[
https://issues.apache.org/jira/browse/SOLR-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924888#comment-13924888
]
Mark Miller commented on SOLR-5823:
---
I rolled this off into SOLR-5834: Overseer threads
[
https://issues.apache.org/jira/browse/SOLR-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-5796.
---
Resolution: Fixed
Lets roll out a perf investigation and other concerns into new issues.
With many
[
https://issues.apache.org/jira/browse/SOLR-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924890#comment-13924890
]
Mark Miller commented on SOLR-5265:
---
bq. We also need a forward compatibility tests
But
Robert Muir created LUCENE-5505:
---
Summary: hunspell SET/FLAG whitespace/BOM handling
Key: LUCENE-5505
URL: https://issues.apache.org/jira/browse/LUCENE-5505
Project: Lucene - Core
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5505:
Attachment: LUCENE-5505.patch
patch with tests.
hunspell SET/FLAG whitespace/BOM handling
Furkan KAMACI created SOLR-5836:
---
Summary: CSVConfig Invalid Check For Equals
Key: SOLR-5836
URL: https://issues.apache.org/jira/browse/SOLR-5836
Project: Solr
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/SOLR-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5836:
Attachment: SOLR-5836.patch
I've added the patch file.
CSVConfig Invalid Check For Equals
Varun Thacker created SOLR-5837:
---
Summary: Add missing equals implementation for SolrDocument,
SolrInputDocument and SolrInputField.
Key: SOLR-5837
URL: https://issues.apache.org/jira/browse/SOLR-5837
[
https://issues.apache.org/jira/browse/SOLR-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-5837:
Attachment: SOLR-5837.patch
Patch Overrides equals() and hashCode() methods of SolrDocument,
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Attachment: SOLR-5829.patch
Add tag/exclude functionality to the ExpandComponent
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Summary: Allow ExpandComponent to accept query and filter query parameters
(was: Add tag/exclude
[
https://issues.apache.org/jira/browse/SOLR-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924904#comment-13924904
]
Yonik Seeley commented on SOLR-5783:
Looking back at the original usecase:
bq. The
Furkan KAMACI created LUCENE-5506:
-
Summary: Ignoring the Return Values Of Immutable Objects
Key: LUCENE-5506
URL: https://issues.apache.org/jira/browse/LUCENE-5506
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated LUCENE-5506:
--
Attachment: LUCENE-5506.patch
Ignoring the Return Values Of Immutable Objects
[
https://issues.apache.org/jira/browse/LUCENE-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924905#comment-13924905
]
Furkan KAMACI commented on LUCENE-5506:
---
I've added patch file.
Ignoring the
[
https://issues.apache.org/jira/browse/SOLR-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI resolved SOLR-5836.
-
Resolution: Fixed
CSVConfig Invalid Check For Equals
--
Hi Simon,
Thanks for the +1. I was afraid that maybe Elasticsearch wants to stay with
Java 6, but I am happy that you will then also change to Java 7 once you use
Lucene 4.8.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
[
https://issues.apache.org/jira/browse/LUCENE-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI resolved LUCENE-5506.
---
Resolution: Fixed
Ignoring the Return Values Of Immutable Objects
From: Robert Muir [mailto:rcm...@gmail.com]
On Sat, Mar 8, 2014 at 8:47 AM, Uwe Schindler u...@thetaphi.de wrote:
And let's also move trunk to Java 8 then.
My suggestion is either:
- Backport all Java 8 changes from trunk to 4.x (and reassign fix
versions to 4.8)
Assuming you mean
Hi;
I've opened an issue an applied a patch for it. Then I've resolved it.
Tooltip says that:
A resolution has been taken, and it is awaiting verification by reporter
However reporter is me :) What is the appropriate workflow for such kind of
things at Lucene/Solr project?
Thanks;
Furkan
Hi all,
Java 8 will get released (hopefully, but I trust the release plan!) on March
18, 2014. Because of this, lots of developers will move to Java 8, too. This
makes maintaining 3 versions for developing Lucene 4.x not easy anymore (unless
you have cool JAVA_HOME cmd launcher scripts using
Hi Furkan,
File a bug report at Atlassian who develops JIRA! I think, there is nothing we
can do about that. We can only globally change the description message for the
“resolved” status – but this would apply for all Apache projects.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63,
[
https://issues.apache.org/jira/browse/SOLR-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924911#comment-13924911
]
Yonik Seeley commented on SOLR-5783:
It looks like one problem is that this patch does
[
https://issues.apache.org/jira/browse/LUCENE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924912#comment-13924912
]
Adrien Grand commented on LUCENE-5502:
--
Thank you Igor, I think this is a very bad
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Description:
By default the ExpandComponent re-runs both the main query and filter queries
to
Hi Uwe;
I will file a bug report. On the other hand I am not a committer yet but I
can resolve an issue if I am the reporter of it. Is this applicable?
Thanks;
Furkan KAMACI
2014-03-08 18:19 GMT+02:00 Uwe Schindler u...@thetaphi.de:
Hi Furkan,
File a bug report at Atlassian who develops
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Description:
By default the ExpandComponent re-runs both the main query and filter queries
to
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Attachment: (was: SOLR-5829.patch)
Allow ExpandComponent to accept query and filter query
Also I think that this should a globally change. If a reporter is not a
committer and resolved an issue message should be different. If it is not
an easy task we can write a generic message for it (i.e. A resolution has
been taken, and it is awaiting verification)
Thanks;
Furkan KAMACI
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Description:
By default the ExpandComponent re-runs both the main query and filter queries
to
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Comment: was deleted
(was: Initial patch leverages the existing tag/exclude framework for
I've opened an issue at Infra.
2014-03-08 18:32 GMT+02:00 Furkan KAMACI furkankam...@gmail.com:
Also I think that this should a globally change. If a reporter is not a
committer and resolved an issue message should be different. If it is not
an easy task we can write a generic message for it
Hi Uwe,
On Sat, Mar 8, 2014 at 5:17 PM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1 I think supporting 2 different versions is hard enough.
[.] Move
On Sat, Mar 8, 2014 at 11:17 AM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7
+1
[.] Move Lucene/Solr trunk to Java 8
-1 , I think it's too early for this.
-Yonik
http://heliosearch.org - native off-heap filters and fieldcache for solr
On Sat, Mar 8, 2014 at 11:41 AM, Adrien Grand jpou...@gmail.com wrote:
[.] Move Lucene/Solr trunk to Java 8 and allow closures in source code. This
would make some APIs much nicer. Our infrastructure mostly supports this,
only ECJ Javadoc linting is not yet possible, but forbidden-apis
[
https://issues.apache.org/jira/browse/LUCENE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924928#comment-13924928
]
ASF subversion and git services commented on LUCENE-5505:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-5505.
-
Resolution: Fixed
Fix Version/s: 5.0
4.8
hunspell SET/FLAG
[
https://issues.apache.org/jira/browse/LUCENE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924931#comment-13924931
]
ASF subversion and git services commented on LUCENE-5505:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924932#comment-13924932
]
Robert Muir commented on SOLR-2934:
---
{quote}
Stephan Meisinger added a comment -
[
https://issues.apache.org/jira/browse/SOLR-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924934#comment-13924934
]
Yonik Seeley commented on SOLR-5783:
Another issue that this change opens up code paths
[
https://issues.apache.org/jira/browse/SOLR-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924937#comment-13924937
]
Mark Miller commented on SOLR-5783:
---
Yeah, there is another fail that may be related to
[
https://issues.apache.org/jira/browse/SOLR-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924938#comment-13924938
]
ASF subversion and git services commented on SOLR-5825:
---
Commit
Furkan KAMACI created SOLR-5838:
---
Summary: Relative SolrHome Path Bug At
AbstractFullDistribZkTestBase
Key: SOLR-5838
URL: https://issues.apache.org/jira/browse/SOLR-5838
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5838:
Attachment: SOLR-5838.patch
I've applied a patch. Also changed that:
{code}
p.append(.. +
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5838:
Fix Version/s: 4.8
Relative SolrHome Path Bug At AbstractFullDistribZkTestBase
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5838:
Affects Version/s: 4.7
4.6.1
Relative SolrHome Path Bug At
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5838:
Priority: Minor (was: Major)
Relative SolrHome Path Bug At AbstractFullDistribZkTestBase
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI resolved SOLR-5838.
-
Resolution: Fixed
Relative SolrHome Path Bug At AbstractFullDistribZkTestBase
[
https://issues.apache.org/jira/browse/SOLR-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5829:
-
Description:
By default the ExpandComponent re-runs both the main query and filter queries
to
Robert Muir created LUCENE-5507:
---
Summary: fix hunspell affix file loading
Key: LUCENE-5507
URL: https://issues.apache.org/jira/browse/LUCENE-5507
Project: Lucene - Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5507:
Attachment: LUCENE-5507.patch
fix hunspell affix file loading
---
[
https://issues.apache.org/jira/browse/SOLR-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924961#comment-13924961
]
Shawn Heisey commented on SOLR-5762:
{quote}
bq.I don't know if we're headed for a
Furkan KAMACI created SOLR-5839:
---
Summary: ZookeeperInfoServlet Does Not Trim Path Properly
Key: SOLR-5839
URL: https://issues.apache.org/jira/browse/SOLR-5839
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5839:
Attachment: SOLR-5839.patch
I've attached the patch file.
ZookeeperInfoServlet Does Not Trim Path
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI resolved SOLR-5839.
-
Resolution: Fixed
ZookeeperInfoServlet Does Not Trim Path Properly
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-5839:
---
Assignee: Mark Miller
ZookeeperInfoServlet Does Not Trim Path Properly
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924978#comment-13924978
]
Mark Miller commented on SOLR-5839:
---
Thanks Furkan!
We should leave the JIRA issue
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924979#comment-13924979
]
ASF subversion and git services commented on SOLR-5839:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924980#comment-13924980
]
ASF subversion and git services commented on SOLR-5839:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-5839.
---
Resolution: Fixed
Fix Version/s: 5.0
ZookeeperInfoServlet Does Not Trim Path Properly
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI reopened SOLR-5838:
-
Relative SolrHome Path Bug At AbstractFullDistribZkTestBase
[
https://issues.apache.org/jira/browse/SOLR-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI reopened SOLR-5836:
-
Reopening issue until a committer commits it.
CSVConfig Invalid Check For Equals
[
https://issues.apache.org/jira/browse/LUCENE-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI reopened LUCENE-5506:
---
Lucene Fields: (was: New)
Reopening issue until a committer commits it.
Ignoring the
[
https://issues.apache.org/jira/browse/SOLR-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5836:
Fix Version/s: 5.0
CSVConfig Invalid Check For Equals
--
[
https://issues.apache.org/jira/browse/LUCENE-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated LUCENE-5506:
--
Fix Version/s: 5.0
Ignoring the Return Values Of Immutable Objects
[
https://issues.apache.org/jira/browse/SOLR-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5838:
Fix Version/s: 5.0
Relative SolrHome Path Bug At AbstractFullDistribZkTestBase
On 3/8/2014 9:17 AM, Uwe Schindler wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1
We might want to wait until 4.9, so we can use the 4.8 release to
announce that the change is coming. My
Furkan KAMACI created SOLR-5840:
---
Summary: UpdateRequest does not check lastCommitWithin and
commitWithin properly
Key: SOLR-5840
URL: https://issues.apache.org/jira/browse/SOLR-5840
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated SOLR-5840:
Attachment: SOLR-5840.patch
I've applied a patch and kept the previous indent for that condition.
[
https://issues.apache.org/jira/browse/SOLR-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-5837:
--
Assignee: Mark Miller
Issue Type: Improvement (was: Bug)
Add missing equals implementation for
[
https://issues.apache.org/jira/browse/SOLR-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924990#comment-13924990
]
Furkan KAMACI commented on SOLR-5840:
-
[~markrmil...@gmail.com] could you check applied
[
https://issues.apache.org/jira/browse/SOLR-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924989#comment-13924989
]
Mark Miller commented on SOLR-5837:
---
Thanks Varun! We should add a couple tests for this
Furkan KAMACI created LUCENE-5508:
-
Summary: Unnecessary Check and Assgiment at FieldFacetStats
Key: LUCENE-5508
URL: https://issues.apache.org/jira/browse/LUCENE-5508
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated LUCENE-5508:
--
Attachment: LUCENE-5508.patch
I've attached the patch. I've also removed an unnecessary field
Thanks Shawn for the support!
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Saturday, March 08, 2014 8:23 PM
To: dev@lucene.apache.org
Subject: Re: [VOTE] Move to Java 7 in Lucene/Solr 4.8, use Java 8 in trunk
(once officially released)
On 3/8/2014 9:17 AM, Uwe Schindler wrote:
[.]
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/9616/
Java: 32bit/jdk1.7.0_51 -server -XX:+UseG1GC
1 tests failed.
REGRESSION: org.apache.lucene.queries.CommonTermsQueryTest.testMinShouldMatch
Error Message:
expected:0 but was:1
Stack Trace:
java.lang.AssertionError: expected:0 but
1 - 100 of 119 matches
Mail list logo
