Hi All,
Our team is using the Solr to process log and we met a problem in SOLR
posting.
We want to detect the health of each core —- whether they are available to
post. We have to figure out ways to do that:
1. Using luke request . —- Cost is a bit high for core loading
2. We have designed
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5568/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.core.TestArbitraryIndexDir.testLoadNewIndexDir
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeExcept
I suspect my picture didn’t make it so I’m trying again:
Or if that didn’t work, I put it on dropbox:
https://www.dropbox.com/s/p3q9ycxytxfqssz/lucene-merge-commit-pic.png?dl=0
~ David
> On Jan 25, 2016, at 1:07 AM, david.w.smi...@gmail.com wrote:
>
>
>
> Just to put a little picture to this
[image: lucene-merge-commit-pic.png]
Just to put a little picture to this, I noticed the following: (see
attached pic)
I suspect it was the bi-product of using a merge based pull (I think the
default?) instead of a rebase one, and as a result we have this little loop
in the log. No doubt there i
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15645/
Java: 64bit/jdk-9-ea+95 -XX:-UseCompressedOops -XX:+UseParallelGC
-XX:-CompactStrings
3 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.client.solrj.io.stream.StreamExpressionTest
Error Message:
Suite timeout
[
https://issues.apache.org/jira/browse/LUCENE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114772#comment-15114772
]
Nicholas Knize commented on LUCENE-6956:
done!
> TestBKDTree.testRandomMedium()
[
https://issues.apache.org/jira/browse/LUCENE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-6956:
---
Attachment: LUCENE-6956.patch
Updated patch that includes all feedback.
> TestBKDTree.testRa
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/353/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.spelling.suggest.SuggesterWFSTTest.testReload
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeExce
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114655#comment-15114655
]
Joel Bernstein edited comment on SOLR-8519 at 1/25/16 2:22 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114655#comment-15114655
]
Joel Bernstein edited comment on SOLR-8519 at 1/25/16 2:20 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114655#comment-15114655
]
Joel Bernstein commented on SOLR-8519:
--
This is looking good.
> Implement ResultSetMe
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1664/
No tests ran.
Build Log:
[...truncated 24453 lines...]
BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:756: The
following error occurred while executing this line:
/x1/jenkins/jenkins-slave/work
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3932/
1 tests failed.
FAILED: org.apache.solr.cloud.OverseerTest.testOverseerFailure
Error Message:
collection1 should be gone after publishing the null state
Stack Trace:
java.lang.AssertionError: collection1 should be gone after
Susheel Kumar created SOLR-8592:
---
Summary: Create collection alias from New UI doesn't actually work
Key: SOLR-8592
URL: https://issues.apache.org/jira/browse/SOLR-8592
Project: Solr
Issue Type
[
https://issues.apache.org/jira/browse/SOLR-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-8591:
-
Description:
Now that we have synchronous streaming and continuous streaming (DaemonStream),
it ma
[
https://issues.apache.org/jira/browse/SOLR-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-8591:
-
Description:
Now that we have synchronous streaming and continuous streaming (DaemonStream),
it ma
[
https://issues.apache.org/jira/browse/SOLR-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-8591:
-
Description:
Now that we have synchronous streaming and continuous streaming (DaemonStream),
it ma
Joel Bernstein created SOLR-8591:
Summary: Add BatchStream to the Streaming API
Key: SOLR-8591
URL: https://issues.apache.org/jira/browse/SOLR-8591
Project: Solr
Issue Type: New Feature
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/5435/
Java: 64bit/jdk1.7.0_80 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication
Error Message:
timed out waiting for collection1 startAt time
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15643/
Java: 64bit/jdk-9-ea+95 -XX:-UseCompressedOops -XX:+UseParallelGC
-XX:-CompactStrings
1 tests failed.
FAILED:
org.apache.solr.handler.component.TestDistributedStatsComponentCardinality.test
Error Message:
int_i: goodEst=13951
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5567/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseG1GC
3 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestLazyCores
Error Message:
ObjectTracker found 4 object(s) that were not released!!!
[MockDi
OK I figured it out ... I had long ago set GIT_AUTHOR_NAME/EMAIL as
env vars ... I think I have it working now, but let's see what I push
next!!
Thanks Uwe, git policeman :)
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jan 24, 2016 at 5:00 PM, Uwe Schindler wrote:
> I have it only fo
I have it only for the single working copies, so my commits at Github or
Forbiddenapis have different names. This is in the .git directory of my working
copy (config) file:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
[
https://issues.apache.org/jira/browse/LUCENE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114557#comment-15114557
]
Michael McCandless commented on LUCENE-6956:
[~nknize] can you fold the rever
Argh!!!
My ~/.gitconfig has:
[user]
email = mikemcc...@apache.org
name = Mike McCandless
Which I think the "git config --global user.name ..." did ...
I'll try to figure why my commits are the wrong username.
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jan 24, 2016 at 4:52 PM
Hi,
you have still the wrong mail address for the GIT commit itsself:
> Author: Michael McCandless
> Authored: Sun Jan 24 16:48:51 2016 -0500
The person who pushed is different:
> Committer: Mike McCandless
> Committed: Sun Jan 24 16:48:51 2016 -0500
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee
I backed out the test improvement that's causing these failures ...
we can add it back with LUCENE-6956.
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jan 24, 2016 at 11:13 AM, Policeman Jenkins Server
wrote:
> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/3034/
> Ja
[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-6938.
---
Resolution: Fixed
Fix Version/s: 5.x
Trunk
Thanks Mark & Dawid! I c
[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114545#comment-15114545
]
Uwe Schindler edited comment on LUCENE-6938 at 1/24/16 9:31 PM:
---
[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-wc-checker.patch
Small update.
> Convert build to work with Git rather
[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-wc-checker.patch
Hi,
here is the former "ant check-svn-working-copy" no
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15642/
Java: 32bit/jdk-9-ea+95 -server -XX:+UseSerialGC -XX:-CompactStrings
2 tests failed.
FAILED: org.apache.lucene.queries.CommonTermsQueryTest.testMinShouldMatch
Error Message:
Stack Trace:
java.lang.AssertionError
at
_
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated SOLR-8519:
---
Attachment: SOLR-8519.patch
Here is an initial patch based on [~joel.bernstein]'s outline. It needs to
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/352/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.update.processor.TestNamedUpdateProcessors.test
Error Message:
java.util.concurrent.TimeoutException: Could not connect to Z
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15641/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseParallelGC
1 tests failed.
FAILED:
org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication
Error Message:
[/home/jenkins/workspace/Lucene-Solr-trunk-Linux/sol
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114462#comment-15114462
]
Kevin Risden commented on SOLR-8519:
Yea that sounds reasonable to me. The JdbcTests mi
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114459#comment-15114459
]
Joel Bernstein commented on SOLR-8519:
--
We can still use the approach of wrapping a Me
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114439#comment-15114439
]
Joel Bernstein commented on SOLR-8519:
--
Ok let's go with #2 with an option to turn it
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114437#comment-15114437
]
Kevin Risden commented on SOLR-8519:
I like #2 since then don't have to worry about con
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114432#comment-15114432
]
Joel Bernstein commented on SOLR-8519:
--
Only thing about #1 is that if there is an emp
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114428#comment-15114428
]
Joel Bernstein edited comment on SOLR-8519 at 1/24/16 6:33 PM:
--
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114428#comment-15114428
]
Joel Bernstein commented on SOLR-8519:
--
That's another option. If we add a header from
Erik Hatcher created SOLR-8590:
--
Summary: example/files improvements
Key: SOLR-8590
URL: https://issues.apache.org/jira/browse/SOLR-8590
Project: Solr
Issue Type: Bug
Components: examp
[
https://issues.apache.org/jira/browse/SOLR-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114418#comment-15114418
]
Joel Bernstein commented on SOLR-8337:
--
Yes
> Add ReduceOperation and wire it into th
Hi,
Sorry, of course I meant "fetch". :-)
Sorry for confusion: I replaced my local branch with the one from origin. There
are several ways to do this:
- Your solution with fetch and then hard reset
- Delete local branch and then pull or fetch
The history is not diverged, I checked this :-) I k
> (as I had no changes in my checkout, I just pulled the branches from remote
> replacing the local one)
I don't know what you did, but it it wasn't pulling ;) Here is a bit
of git parlance overview:
- You "fetch" new commits and reference updates (git fetch origin).
- A "pull" is basically fetc
[
https://issues.apache.org/jira/browse/SOLR-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114396#comment-15114396
]
Kevin Risden commented on SOLR-8337:
So that means that the RecordCountStream file can
[
https://issues.apache.org/jira/browse/SOLR-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114395#comment-15114395
]
Joel Bernstein commented on SOLR-8337:
--
It was conflicting with the count metric funct
Hi,
Thanks!
(as I had no changes in my checkout, I just pulled the branches from remote
replacing the local one)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Dawid Weiss [mailto:dawid.we...@gma
[
https://issues.apache.org/jira/browse/SOLR-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114389#comment-15114389
]
Kevin Risden commented on SOLR-8337:
[~joel.bernstein] - Any reason that this patch rem
Build: https://builds.apache.org/job/Lucene-Solr-Maven-5.x/1164/
No tests ran.
Build Log:
[...truncated 28192 lines...]
BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-5.x/build.xml:701: The
following error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspac
Hello,
Several people reported problems with the fact that git history
included the "wipeout-and-revert" pair of commits imported from the
SVN history. The problems seem to be:
1) every file has a pair of two commits (removal/ restore),
2) not every tool shows file history past the removal point
THANKS!
On Sun, Jan 24, 2016 at 11:26 AM Dawid Weiss wrote:
> I will do it.
>
> D.
>
> On Sun, Jan 24, 2016 at 3:06 PM, Uwe Schindler wrote:
> > Hi,
> >
> > I tried it out locally: It is quite easy to use "rebase" and step over
> those 2 commits. So you can just remove them, because they are tog
I will do it.
D.
On Sun, Jan 24, 2016 at 3:06 PM, Uwe Schindler wrote:
> Hi,
>
> I tried it out locally: It is quite easy to use "rebase" and step over those
> 2 commits. So you can just remove them, because they are together basically a
> no-op (remove all and then add all back).
>
> I can do
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/3034/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.lucene.search.TestLatLonPointQueries.testAllLatEqual
Error Message:
Captured an uncaught exception in thread: Thread[id=23,
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114366#comment-15114366
]
Kevin Risden commented on SOLR-8519:
I've been using git and creating patches previous
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15639/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.lucene.search.TestLatLonPointQueries.testMultiValued
Error Message:
some hits were wrong
Stack Trace:
java.lang.AssertionError:
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114363#comment-15114363
]
Kevin Risden commented on SOLR-8519:
Hmmm I think that adding metadata to the first tup
[
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114353#comment-15114353
]
Joel Bernstein commented on SOLR-8519:
--
We can use this ticket to workout the git work
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/918/
1 tests failed.
FAILED: org.apache.lucene.search.TestLatLonPointQueries.testRandomBig
Error Message:
Captured an uncaught exception in thread: Thread[id=69, name=T1,
state=RUNNABLE, group=TGRP-TestLatLonPointQueries]
Stac
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15336/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.security.BasicAuthIntegrationTest.testBasics
Error Message:
must have failed
Stack Trace:
java.lang.AssertionError: must have failed
Hi,
I tried it out locally: It is quite easy to use "rebase" and step over those 2
commits. So you can just remove them, because they are together basically a
no-op (remove all and then add all back).
I can do that for both branches and then do a "git push --force" of the
rewritten history? An
Ok, got it. Thanks!
Joel Bernstein
http://joelsolr.blogspot.com/
On Sun, Jan 24, 2016 at 7:58 AM, Daniel Gruno wrote:
> You can't merge directly on GitHub - they only host a read-only mirror of
> the repo.
> There are however command-line options for merging, which you can see on
> the PR page.
[
https://issues.apache.org/jira/browse/SOLR-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114311#comment-15114311
]
Jamie Johnson commented on SOLR-8466:
-
I like the approach as it's much less invasive.
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/793/
1 tests failed.
FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication
Error Message:
timed out waiting for collection1 startAt time to exceed: Sun Jan 24 04:10:56
PST 2016
Stack Trace:
java.lang.As
You can't merge directly on GitHub - they only host a read-only mirror of the
repo.
There are however command-line options for merging, which you can see on the PR
page.
Other than that, you can mark something as merged by putting "This fixes (or
closes, merges etc) #1234" where 1234 is the issu
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/346/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
2 tests failed.
FAILED: org.apache.lucene.queries.CommonTermsQueryTest.testExtend
Error Message:
expected:<[2]> but was:<[0]>
Stack Trace:
org.junit.ComparisonF
I pushed a fix ... it was because memory and direct DV formats were
illegally using an IndexInput from one thread while cloning it from
another thread.
I also tried to improve RAMInputStream's EOFE exception messages to
differentiate the two cases.
Mike McCandless
http://blog.mikemccandless.com
What's the error? I don't think you can still merge into Github, it remains
read-only..
On 24 Jan 2016 03:59, "Joel Bernstein" wrote:
> I had no problem pushing my first commit. But I didn't seem to have
> permission to merge a pull-request from Github. Is there another layer of
> permissions tha
[
https://issues.apache.org/jira/browse/LUCENE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michele Renda updated LUCENE-6990:
--
External issue URL: https://jira.mongodb.org/browse/JAVA-2098
> Mongo 3.x Directory support
> -
Michele Renda created LUCENE-6990:
-
Summary: Mongo 3.x Directory support
Key: LUCENE-6990
URL: https://issues.apache.org/jira/browse/LUCENE-6990
Project: Lucene - Core
Issue Type: Improvement
Uwe Schindler created LUCENE-6989:
-
Summary: Implement MMapDirectory unmapping for coming Java 9
changes
Key: LUCENE-6989
URL: https://issues.apache.org/jira/browse/LUCENE-6989
Project: Lucene - Core
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15636/
Java: 32bit/jdk-9-ea+95 -client -XX:+UseG1GC -XX:-CompactStrings
1 tests failed.
FAILED: org.apache.lucene.search.TestLatLonPointQueries.testRandomMedium
Error Message:
Captured an uncaught exception in thread: Thread[id=41, na
Build: https://builds.apache.org/job/Lucene-Solr-Maven-5.x/1163/
No tests ran.
Build Log:
[...truncated 25578 lines...]
BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-5.x/build.xml:701: The
following error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspac
I'll dig.
Mike McCandless
http://blog.mikemccandless.com
On Sat, Jan 23, 2016 at 7:57 PM, Policeman Jenkins Server
wrote:
> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15631/
> Java: 64bit/jdk-9-ea+95 -XX:+UseCompressedOops -XX:+UseParallelGC
> -XX:-CompactStrings
>
> 1 test
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/917/
3 tests failed.
FAILED: org.apache.solr.cloud.BasicDistributedZkTest.test
Error Message:
Error from server at http://127.0.0.1:41610/_hr/collection1: Bad Request
request:
http://127.0.0.1:33848/_hr/collection1/update?u
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15333/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseG1GC
2 tests failed.
FAILED: org.apache.lucene.queries.CommonTermsQueryTest.testMinShouldMatch
Error Message:
Stack Trace:
java.lang.AssertionError
at
__randomizedtesting.SeedInf
I don't know.
Dawid
On Sun, Jan 24, 2016 at 4:59 AM, Joel Bernstein wrote:
> I had no problem pushing my first commit. But I didn't seem to have
> permission to merge a pull-request from Github. Is there another layer of
> permissions that need to be setup for this?
>
> Joel Bernstein
> http://j
We can move the reference for master and branch_5x -- these are
affected. I can do it tonight and cherry pick any commits that have
been added since then.
Dawid
On Sun, Jan 24, 2016 at 7:07 AM, david.w.smi...@gmail.com
wrote:
> I'm seeing this too Yonik :-( This really sucks. I googled and fou
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/3033/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.TestDistributedSearch.test
Error Message:
Error from server at http://127.0.0.1:57837//collection1:
java.lang.NullPointerExce
[
https://issues.apache.org/jira/browse/SOLR-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-8466:
---
Attachment: SOLR-8466.patch
ok. Attaching [^SOLR-8466.patch]. I understood an encapsulation cha
81 matches
Mail list logo