[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6514:
-
Attachment: SOLR-6514.patch
should not cache collections inside clusterstate.json
> SyncSliceTest on trunk
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132584#comment-14132584
]
Noble Paul edited comment on SOLR-6514 at 9/13/14 6:58 AM:
---
solrj
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11235/
Java: 32bit/jdk1.8.0_40-ea-b04 -client -XX:+UseG1GC
1 tests failed.
REGRESSION:
org.apache.solr.cloud.DeleteLastCustomShardedReplicaTest.testDistribSearch
Error Message:
No live SolrServers available to handle this
request:[h
@Ryan: Yes, I'm clear that you're talking about trunk/5.0
The point remains though that once trunk starts down that
path keeping the branches in synch becomes harder. Does
the ease in development (alleged) with Java8 balance well
against dealing with that divergence? Maybe so, but let's
consider it
I dug some more into this, and e.g. compared how does PhraseQuery behave on
these cases ('a' and 'b' are indexed at the same position):
"a b" - NO MATCH (expected)
"a b"~1+ (1+ - any slop >= 1) - MATCH
Because of the mathematics behind PQ, the slop determines the edit distance
to match 'a' and 'b
[
https://issues.apache.org/jira/browse/LUCENE-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132554#comment-14132554
]
Shai Erera commented on LUCENE-5941:
bq. Well i think its related to windows.
The on
[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132538#comment-14132538
]
Noble Paul commented on SOLR-5473:
--
[~mewmewball] Can you please open a ticket and we can
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132502#comment-14132502
]
Noble Paul commented on SOLR-6514:
--
Seems to be a bug with CloudSolrServer , it worked fin
[
https://issues.apache.org/jira/browse/SOLR-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132497#comment-14132497
]
Shalin Shekhar Mangar commented on SOLR-6509:
-
bq. that said: i'm not convinced
I’ve worked on commercial libraries, and the releases were limited to the
oldest JVM that our big customers were using. Some customers were much more
conservative (or lazy) than I imagined.
I just sent out an e-mail about planning for the JDK 8 upgrade and got some
skepticism in reply. In a pro
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11234/
Java: 32bit/jdk1.7.0_67 -server -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 31754 lines...]
-check-forbidden-all:
[forbidden-apis] Reading bundled API signatures: jdk-unsafe-1.7
[forbidden-apis] Reading bundled AP
On Fri, Sep 12, 2014 at 1:39 PM, Ryan Ernst wrote:
> I think the question here is, should trunk be the "blazing forefront of
> development?"
Even if the answer is "yes", In what dimensions though? Blazing
forefront of lucene/solr need not be blazing forefront of Java or of
different operating sy
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe resolved LUCENE-5930.
Resolution: Fixed
Fix Version/s: 5.0
4.11
Assignee: Steve Rowe
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132470#comment-14132470
]
ASF subversion and git services commented on LUCENE-5930:
-
Commit
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java7/4847/
1 tests failed.
REGRESSION: org.apache.solr.cloud.SyncSliceTest.testDistribSearch
Error Message:
expected:<5> but was:<4>
Stack Trace:
java.lang.AssertionError: expected:<5> but was:<4>
at
__randomizedtesting.Seed
There are so many new features in java 8. lambdas etc. If devs start using
those features in trunk and the 4x branch sticks to java 7 the codebase can
diverge quite a bit. Which means patches won't apply across branches. I'm
all for moving to java 8 . but is it not possible to move both?
On Sat, S
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-6514:
---
Attachment: SOLR-6514.patch
Handles the NPE but not the "SolrException: Not enough nodes to handle the
Anshum Gupta created SOLR-6516:
--
Summary: Use SolrJ collection API methods in SolrCloud tests
wherever possible
Key: SOLR-6516
URL: https://issues.apache.org/jira/browse/SOLR-6516
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-6514:
Assignee: Noble Paul
> SyncSliceTest on trunk is failing consistently
>
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/4308/
Java: 32bit/jdk1.8.0_40-ea-b04 -client -XX:+UseParallelGC
1 tests failed.
REGRESSION:
org.apache.solr.cloud.DeleteLastCustomShardedReplicaTest.testDistribSearch
Error Message:
No live SolrServers available to handle this requ
[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132444#comment-14132444
]
Robert Muir commented on LUCENE-5940:
-
{quote}
The meta tool I have proposed could b
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132443#comment-14132443
]
Anshum Gupta commented on SOLR-6514:
Even on fixing the NPE (by adding checking), the t
Forbidden-apis doesn’t like the String(byte[]) ctor in Overseer.java:316,
committed by Noble in r1624556 (‘ant precommit’ would have caught this):
311: byte[] data = ZkStateReader.toJSON(e.getValue());
[…]
316: log.info("going to create_collection {}", e.getKey(), new String(data));
-
[mvn]
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1206/
All tests passed
Build Log:
[...truncated 47112 lines...]
BUILD FAILED
/usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:514:
The following error occurred while executing this line:
/usr/home/jenkins/jen
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132409#comment-14132409
]
Steve Rowe edited comment on LUCENE-5930 at 9/13/14 12:57 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132409#comment-14132409
]
Steve Rowe commented on LUCENE-5930:
Commit 1624689 from [~sar...@syr.edu] in branch
[
https://issues.apache.org/jira/browse/SOLR-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-5930:
-
Comment: was deleted
(was: Commit 1624689 from [~sar...@syr.edu] in branch 'dev/trunk'
[ https://svn.apache
[
https://issues.apache.org/jira/browse/SOLR-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132407#comment-14132407
]
ASF subversion and git services commented on SOLR-5930:
---
Commit 16246
[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132382#comment-14132382
]
Robert Muir commented on LUCENE-5940:
-
Actually 5.0 doesn't even need to read 4.x ind
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132350#comment-14132350
]
Anshum Gupta commented on SOLR-6514:
It's an NPE from what looks like the 5473/74 commi
>
> I agree we have to move forward at some point. I'm
not convinced now's the time as far as Java 8 is concerned though
I am not suggesting moving the stable branch to java 8, only trunk. Your
statement implies I am suggesting moving the entire project to java 8. I
don't think everyone is und
[
https://issues.apache.org/jira/browse/SOLR-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-6249:
-
Attachment: SOLR-6249.patch
Here's a patch that gives a client the option to wait a max number of s
On Fri, Sep 12, 2014 at 7:32 PM, Erick Erickson wrote:
> Users don't care about lambda expressions.
You cannot say this. Users of lucene are API users, and supporting
these language changes well are important.
-
To unsubscribe,
I'd like to avoid the distraction of speculating about the reasons
organizations will or won't upgrade to Java 8 as I don't think it's
helpful.
What's important to me is whether Java 8 offers me, in my role of
supporting real-live users, benefit. And here I don't care about
lambda expressions. Use
[
https://issues.apache.org/jira/browse/SOLR-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Chanan updated SOLR-6515:
-
Attachment: SOLR-6515.patch
> Document/log SolrZkClient.clean semantics with nodes being added conc
Gregory Chanan created SOLR-6515:
Summary: Document/log SolrZkClient.clean semantics with nodes
being added concurrently
Key: SOLR-6515
URL: https://issues.apache.org/jira/browse/SOLR-6515
Project: So
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11233/
Java: 64bit/jdk1.8.0_20 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
REGRESSION: org.apache.solr.cloud.SyncSliceTest.testDistribSearch
Error Message:
expected:<5> but was:<4>
Stack Trace:
java.lang.AssertionError: e
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132261#comment-14132261
]
ASF subversion and git services commented on LUCENE-5930:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132257#comment-14132257
]
Ryan Ernst commented on LUCENE-5930:
+1, thanks Steve!
> IntelliJ config: drop resou
Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/31011/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.lucene.index.TestBackwardsCompatibility3x
Error Message:
MockDirectoryWrapper: cannot close: there are still open files: {_2_1.s0=1,
_0.frq=1, _1.fdx=1, _3.fdt
[
https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5930:
---
Attachment: LUCENE-5930.failed.intellij.map-reduce.module.test.output.txt
LUCENE-5930.
I pushed a fix.
On Fri, Sep 12, 2014 at 3:36 PM, wrote:
> Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/31010/
>
> 2 tests failed.
> FAILED:
> junit.framework.TestSuite.org.apache.lucene.index.TestBackwardsCompatibility3x
>
> Error Message:
> MockDirectoryWrapper: cannot clo
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132248#comment-14132248
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132244#comment-14132244
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/31010/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.lucene.index.TestBackwardsCompatibility3x
Error Message:
MockDirectoryWrapper: cannot close: there are still open files: {_0.tvx=1,
_0.fdt=1, _1.tvx=1, _0.fdx=
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132221#comment-14132221
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst resolved LUCENE-5939.
Resolution: Fixed
Fix Version/s: 5.0
4.11
4.10.1
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132219#comment-14132219
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132218#comment-14132218
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132209#comment-14132209
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132204#comment-14132204
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132200#comment-14132200
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132198#comment-14132198
]
Robert Muir commented on LUCENE-5945:
-
Also zip file handling isnt fixed yet in TestU
[
https://issues.apache.org/jira/browse/LUCENE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5945:
Attachment: LUCENE-5945_core.patch
Here is a start, lucene/core src and tests, and test-framework.
[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132185#comment-14132185
]
Steve Rowe commented on SOLR-5473:
--
{{SyncSliceTest}} started failing after the r1624556 c
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132181#comment-14132181
]
Steve Rowe commented on SOLR-6514:
--
I did {{svn up -r1624555}} (the revision just before [
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132179#comment-14132179
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132150#comment-14132150
]
Hoss Man commented on SOLR-6509:
bq. Although I don't know if this qualifies as a major bug
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132145#comment-14132145
]
Steve Rowe commented on SOLR-6514:
--
from {{svn info}}:
bq. Revision: 1624653
java -versi
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132131#comment-14132131
]
Anshum Gupta edited comment on SOLR-6514 at 9/12/14 9:32 PM:
-
D
[
https://issues.apache.org/jira/browse/SOLR-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132139#comment-14132139
]
Timothy Potter commented on SOLR-6509:
--
Good catch! Although I don't know if this qual
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132131#comment-14132131
]
Anshum Gupta commented on SOLR-6514:
Does this fail only on Java 8? I'm running 7 and t
[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132126#comment-14132126
]
Jessica Cheng Mallet commented on SOLR-5473:
Hey guys, under heavy load-testing
[
https://issues.apache.org/jira/browse/SOLR-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter reassigned SOLR-6249:
Assignee: Timothy Potter
> Schema API changes return success before all cores are updated
>
[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132120#comment-14132120
]
ASF subversion and git services commented on LUCENE-5939:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132117#comment-14132117
]
ASF subversion and git services commented on SOLR-5810:
---
Commit 16246
[
https://issues.apache.org/jira/browse/SOLR-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132116#comment-14132116
]
ASF subversion and git services commented on SOLR-5474:
---
Commit 16246
[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132115#comment-14132115
]
ASF subversion and git services commented on SOLR-5473:
---
Commit 16246
Your arguments really resonate with me, Ryan…
+1 to Java 8
(FWIW I’m using coding in Java 8 these days already)
~ David Smiley
Freelance Apache Lucene/Solr Search Consultant/Developer
http://www.linkedin.com/in/davidwsmiley
On Fri, Sep 12, 2014 at 1:39 PM, Ryan Ernst wrote:
> One that is on my
"Corporate overlords" isn't helpful. Lucene is what it is because of its
wide adoption. That includes big, small, smart, and stupid organizations. I
don't think that an infrastructure component like Lucene needs to be 'ahead
of the curve'. It should aim to be widely adoptable. To me, that means
mov
>
> One that is on my mind right now may just barely make it to 1.7 this year.
>
> Thus my desire to see a way to get the pending trunk work to people who
> are not moving to 1.8 any time soon.
We should not hold Lucene back because some companies have arcane upgrade
policies. Part of what al
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132068#comment-14132068
]
Steve Rowe commented on SOLR-6514:
--
branch_4x does not have the same issue.
> SyncSliceTe
[
https://issues.apache.org/jira/browse/SOLR-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6514:
-
Affects Version/s: 5.0
> SyncSliceTest on trunk is failing consistently
> -
Steve Rowe created SOLR-6514:
Summary: SyncSliceTest on trunk is failing consistently
Key: SOLR-6514
URL: https://issues.apache.org/jira/browse/SOLR-6514
Project: Solr
Issue Type: Bug
On Fri, Sep 12, 2014 at 3:35 PM, Robert Muir wrote:
> On Fri, Sep 12, 2014 at 3:31 PM, Chris Hostetter
> wrote:
> >
> > b) that your argument against benson's claims seemed missleading: just
> > because Oracle is EOLing doesn't mean people won't be using OpenJDK; even
> > if they are using Oracl
Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-Java7/2102/
1 tests failed.
REGRESSION: org.apache.solr.client.solrj.TestLBHttpSolrServer.testReliability
Error Message:
No live SolrServers available to handle this request
Stack Trace:
org.apache.solr.client.solrj.SolrServerException:
[
https://issues.apache.org/jira/browse/LUCENE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132016#comment-14132016
]
Robert Muir commented on LUCENE-5945:
-
There is a little complexity, today its not so
I'm ok with moving to Java 8, although realistically I don't think
it's that much of a gain (yes, there are some syntactic sugars and new
APIs, but I remain pretty conservative about using them).
D.
On Fri, Sep 12, 2014 at 9:35 PM, Robert Muir wrote:
> On Fri, Sep 12, 2014 at 3:31 PM, Chris Host
[
https://issues.apache.org/jira/browse/LUCENE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131997#comment-14131997
]
Dawid Weiss commented on LUCENE-5945:
-
Pretty cool idea!
> Full cutover to Path api
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/1827/
Java: 64bit/jdk1.7.0 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
REGRESSION:
org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testDistribSearch
Error Message:
Error CREATEing SolrCore 'halfcollection_shard1_replic
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11232/
Java: 64bit/jdk1.7.0_67 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 20308 lines...]
BUILD FAILED
/mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:491: The following
error
On Fri, Sep 12, 2014 at 3:31 PM, Chris Hostetter
wrote:
>
> b) that your argument against benson's claims seemed missleading: just
> because Oracle is EOLing doesn't mean people won't be using OpenJDK; even
> if they are using Oracle's JDK, if they are large comercial organizations
> they might pa
: That is bogus for an open source project. I won't have such updates,
: how can i support such a java version, users that run into trouble?
: And this does happen often.
: I don't think i should have to pay money and become a paying customer
: to Oracle to support lucene.
I didn't say you should
+1
On Fri, Sep 12, 2014 at 9:26 PM, Michael McCandless
wrote:
> +1
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Fri, Sep 12, 2014 at 11:41 AM, Ryan Ernst wrote:
>> It has been 6 months since Java 8 was released. It has proven to be
>> both stable (no issues like with the init
+1
Mike McCandless
http://blog.mikemccandless.com
On Fri, Sep 12, 2014 at 11:41 AM, Ryan Ernst wrote:
> It has been 6 months since Java 8 was released. It has proven to be
> both stable (no issues like with the initial release of java 7) and
> faster. And there are a ton of features that wou
On Fri, Sep 12, 2014 at 3:19 PM, Chris Hostetter
wrote:
> Playing devils advocate
>
>> http://www.oracle.com/technetwork/java/eol-135779.html
>
> That same page that makes it clear there will not longer be *public* (ie:
> free) "updates of Java SE 7" from oracle past that date, it also makes
On Fri, Sep 12, 2014 at 3:13 PM, Tommaso Teofili
wrote:
>
>
>
> 2014-09-12 21:11 GMT+02:00 Robert Muir :
>>
>> On Fri, Sep 12, 2014 at 2:39 PM, Chris Hostetter
>> wrote:
>> >
>> > : faster. And there are a ton of features that would make our lives as
>> > : developers easier (and that can improv
[
https://issues.apache.org/jira/browse/SOLR-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131972#comment-14131972
]
Timothy Potter commented on SOLR-6511:
--
bq. what ought to happen here is that replica2
: "After April 2015, Oracle will no longer post updates of Java SE 7 to
: its public download sites"
I'm not sure that's really relevant to the discussion?
With Java5 & Java6, there was no other large scale JVM distributions then
Oracle, so their EOL was extermely pertinant to the question of ho
2014-09-12 21:11 GMT+02:00 Robert Muir :
> On Fri, Sep 12, 2014 at 2:39 PM, Chris Hostetter
> wrote:
> >
> > : faster. And there are a ton of features that would make our lives as
> > : developers easier (and that can improve the quality of Lucene 5 when
> > : it is eventually released).
> >
> >
On Fri, Sep 12, 2014 at 2:39 PM, Chris Hostetter
wrote:
>
> : faster. And there are a ton of features that would make our lives as
> : developers easier (and that can improve the quality of Lucene 5 when
> : it is eventually released).
>
> Examples please?
>
>
The ability to specify default meth
[
https://issues.apache.org/jira/browse/SOLR-6508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe resolved SOLR-6508.
--
Resolution: Fixed
Fix Version/s: 5.0
4.11
Committed to trunk and branch_4x.
>
[
https://issues.apache.org/jira/browse/SOLR-6508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131956#comment-14131956
]
ASF subversion and git services commented on SOLR-6508:
---
Commit 16246
On Fri, Sep 12, 2014 at 2:48 PM, Benson Margulies wrote:
> If we release the current contents of trunk first, I'm OK with this, not
> that i have a veto. There are many large organizations of the sort that use
> Lucene & Solr that will not be moving to 8 for years yet. If the current
> trunk conte
[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131951#comment-14131951
]
Tim Smith commented on LUCENE-5940:
---
i fully understand the reasons for wanting to chan
[
https://issues.apache.org/jira/browse/SOLR-6508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131945#comment-14131945
]
ASF subversion and git services commented on SOLR-6508:
---
Commit 16246
Erick Erickson created SOLR-6513:
Summary: Add a collectionsAPI call ASSIGNPREFERREDLEADERS
Key: SOLR-6513
URL: https://issues.apache.org/jira/browse/SOLR-6513
Project: Solr
Issue Type: Impro
[
https://issues.apache.org/jira/browse/SOLR-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta reassigned SOLR-6248:
--
Assignee: Anshum Gupta
> MoreLikeThis Query Parser
> -
>
>
[
https://issues.apache.org/jira/browse/SOLR-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-6511:
-
Attachment: SOLR-6511.patch
Here's a patch to address this problem, specifically it does:
1) tries
If we release the current contents of trunk first, I'm OK with this, not
that i have a veto. There are many large organizations of the sort that use
Lucene & Solr that will not be moving to 8 for years yet. If the current
trunk content is marooned until they move to 8, I will be sad.
On Fri, Sep 1
1 - 100 of 148 matches
Mail list logo
