Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15216/
Java: 32bit/jdk-9-ea+95 -server -XX:+UseParallelGC -XX:-CompactStrings
1 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Error from server at http://127.0.0.1:58927/p_ew/c/awholyn
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/701/
3 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestLazyCores
Error Message:
ERROR: SolrIndexSearcher opens=51 closes=50
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearcher opens=51 closes
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.x/408/
No tests ran.
Build Log:
[...truncated 53104 lines...]
prepare-release-no-sign:
[mkdir] Created dir:
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/lucene/build/smokeTestRelease/dist
[copy] Copying
[
https://issues.apache.org/jira/browse/SOLR-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-8419:
---
Attachment: SOLR_8419.patch
The attach patch:
* Fixes the invalid/confusing response when there's a dis
[
https://issues.apache.org/jira/browse/SOLR-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-8419:
---
Issue Type: Bug (was: Improvement)
> TermVectorComponent distributed-search issues
> -
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15215/
Java: 32bit/jdk1.8.0_66 -client -XX:+UseParallelGC
1 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.cloud.TestMiniSolrCloudClusterSSL
Error Message:
Suite timeout exceeded (>= 720 msec).
Stack Trace:
java
In a normal query multiple fl parameters are additive, but they
collectively override whatever fl parameter(s) may have been specified in
"defaults", right? I mean, that's why Solr has "appends" in addition to
"defaults", right"?
Ah, but I see in the JSON Request API doc that it says "Multi-valued
[
https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059442#comment-15059442
]
Joel Bernstein edited comment on SOLR-8191 at 12/16/15 3:37 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059442#comment-15059442
]
Joel Bernstein commented on SOLR-8191:
--
Sure, I should have some time review this tick
[
https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059422#comment-15059422
]
Jason Gerlowski commented on SOLR-8191:
---
After a little more attention, I think it'd
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/1047/
3 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
KeeperErrorCode = ConnectionLoss for /clusterstate.json
Stack Trace:
org.apache.zookeeper.KeeperException$ConnectionLossExcep
Multiple "fl" parameters are additive, so it would make sense that
"fields" is also (for fl and field in the same request). If that's
true for "fl" as a default and "fl" as a query param, then it seems
like that should be true for the other variants.
If "fl" as a query param and "fl" in a JSON pa
[
https://issues.apache.org/jira/browse/SOLR-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arcadius Ahouansou updated SOLR-7964:
-
Attachment: SOLR_7964.patch
- Fixed code to allow highlighting while building final Solr re
Hi folks:
I am interested in using the SortingLeafReader to sort my index. According
to examples, calling IndexWriter.addIndexes on the wrapper
SortingLeafReader would do the trick.
In the recent releases, IndexWriter.addIndexes api is now only taking a
CodecReader. Is there another way to do ind
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/260/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED:
org.apache.solr.cloud.OverseerTest.testExternalClusterStateChangeBehavior
Error Message:
Illegal state, was: down expected:active cluste
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15214/
Java: 32bit/jdk1.8.0_66 -client -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.SyncSliceTest.test
Error Message:
timeout waiting to see all nodes active
Stack Trace:
java.lang.AssertionError: timeout wai
[
https://issues.apache.org/jira/browse/SOLR-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arcadius Ahouansou updated SOLR-7964:
-
Description:
When using the new suggester context filtering query param
{{suggest.contextF
Yonik? The doc is weak in this area. In fact, I see a comment on it from
Cassandra directed to you to verify the JSON to parameter mapping. It would
be nice to have a clear statement of the semantics for JSON "fields"
parameter and how it may or may not interact with the Solr fl parameter.
-- Jack
[
https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059213#comment-15059213
]
Jason Gerlowski commented on SOLR-8191:
---
The current patch still applies cleanly. Fi
Nirmala Venkatraman created SOLR-8422:
-
Summary: Basic Authentication plugin is not working correctly in
solrcloud
Key: SOLR-8422
URL: https://issues.apache.org/jira/browse/SOLR-8422
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski updated SOLR-8190:
--
Attachment: SOLR-8190.patch
Would be nice to get this rolling again. To keep it up to date, I've
[
https://issues.apache.org/jira/browse/SOLR-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059140#comment-15059140
]
Hoss Man commented on SOLR-8421:
tomas: sure, and maybe (in a weird situation) that's a tot
[
https://issues.apache.org/jira/browse/SOLR-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059131#comment-15059131
]
Tomás Fernández Löbbe commented on SOLR-8421:
-
I thought about it. I believe th
[
https://issues.apache.org/jira/browse/SOLR-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059132#comment-15059132
]
Hoss Man commented on SOLR-8421:
At a minimum, after parsing the zkhosts but before any zk
[
https://issues.apache.org/jira/browse/SOLR-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-8421:
---
Description:
If a user mistakenly tries to specify the chroot on every zk host:port in the
zkhosts string, th
[
https://issues.apache.org/jira/browse/SOLR-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reopened SOLR-8421:
why don't we re-purpose this issue to try and make the error/logging more clear
about what's happening in these
[
https://issues.apache.org/jira/browse/SOLR-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomás Fernández Löbbe closed SOLR-8421.
---
Resolution: Not A Problem
chroot needs to be added only once after the list of hosts, n
[
https://issues.apache.org/jira/browse/SOLR-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059047#comment-15059047
]
Tomás Fernández Löbbe commented on SOLR-7996:
-
[~jej2003] (in reply to [this
e
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/2889/
Java: 64bit/jdk1.7.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
2 tests failed.
FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test
Error Message:
Captured an uncaught exception in thread: Thread[id=9021, name=Thr
Dmitry Myaskovskiy created SOLR-8421:
Summary: zkHost with chroot and multiple hosts not working
Key: SOLR-8421
URL: https://issues.apache.org/jira/browse/SOLR-8421
Project: Solr
Issue Ty
[
https://issues.apache.org/jira/browse/SOLR-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-8395:
---
Attachment: SOLR-8395.patch
It's nearly shocked me. The first path with multivalue fields ("uid
[
https://issues.apache.org/jira/browse/SOLR-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058928#comment-15058928
]
Romit Singhai edited comment on SOLR-8374 at 12/15/15 10:07 PM:
-
[
https://issues.apache.org/jira/browse/SOLR-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058928#comment-15058928
]
Romit Singhai commented on SOLR-8374:
-
Hi Varun,
This information will be useful for p
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14915/
Java: 64bit/jdk1.7.0_80 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.search.ReturnFieldsTest.testToString
Error Message:
expected:<...s=[],fields=[score, [test, id],okFieldNames=[null, sc
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058884#comment-15058884
]
ASF subversion and git services commented on SOLR-8388:
---
Commit 17202
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2944/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED:
org.apache.solr.handler.PingRequestHandlerTest.testPingInClusterWithNoHealthCheck
Error Message:
No live SolrServers available to handle this
re
[
https://issues.apache.org/jira/browse/SOLR-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-8372.
Resolution: Fixed
Fix Version/s: Trunk
5.5
> Canceled recovery can lead to
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/700/
3 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestLazyCores
Error Message:
ERROR: SolrIndexSearcher opens=51 closes=50
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearcher opens=51 closes
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058828#comment-15058828
]
ASF subversion and git services commented on SOLR-8388:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058814#comment-15058814
]
ASF subversion and git services commented on SOLR-8372:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058808#comment-15058808
]
ASF subversion and git services commented on SOLR-8372:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev resolved SOLR-7730.
Resolution: Fixed
> speed-up faceting on doc values fields
>
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058798#comment-15058798
]
ASF subversion and git services commented on SOLR-7730:
---
Commit 17202
[
https://issues.apache.org/jira/browse/LUCENE-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058762#comment-15058762
]
Paul Elschot commented on LUCENE-6926:
--
I tried implementing this NOT wrapper, but i
[
https://issues.apache.org/jira/browse/SOLR-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-8395:
---
Summary: query-time join (with scoring) for numeric fields (was:
query-time join for numeric f
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058747#comment-15058747
]
ASF subversion and git services commented on SOLR-7730:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058739#comment-15058739
]
ASF subversion and git services commented on SOLR-7730:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058733#comment-15058733
]
Mark Miller commented on SOLR-8415:
---
bq. Docs should go on the wiki somewhere.
I'd start
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/5344/
Java: 64bit/jdk1.7.0_80 -XX:-UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.search.ReturnFieldsTest.testToString
Error Message:
expected:<...s=(globs=[],fields=[[score, test, id],okFieldNames=[null, score
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3838/
1 tests failed.
FAILED: org.apache.solr.search.ReturnFieldsTest.testToString
Error Message:
expected:<...s=(globs=[],fields=[[score, test, id],okFieldNames=[null, score,
test, id]],reqFieldNames=[id,...> but was:<...s=(globs
[
https://issues.apache.org/jira/browse/SOLR-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Hill updated SOLR-8420:
---
Attachment: 0001-Fix-overflow-in-date-statistics.patch
One line fix, plus tests.
> Date statistics: sumOfSquar
[
https://issues.apache.org/jira/browse/SOLR-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Hill updated SOLR-8420:
---
Comment: was deleted
(was: One line fix, plus tests.)
> Date statistics: sumOfSquares overflows long
> ---
Tom Hill created SOLR-8420:
--
Summary: Date statistics: sumOfSquares overflows long
Key: SOLR-8420
URL: https://issues.apache.org/jira/browse/SOLR-8420
Project: Solr
Issue Type: Bug
Compone
David Smiley created SOLR-8419:
--
Summary: TermVectorComponent distributed-search issues
Key: SOLR-8419
URL: https://issues.apache.org/jira/browse/SOLR-8419
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SOLR-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058606#comment-15058606
]
Hoss Man commented on SOLR-3229:
I don't remember this issue at all, and w/o digging into i
[
https://issues.apache.org/jira/browse/SOLR-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated SOLR-8415:
Attachment: SOLR-8415.patch
Attaching a new patch that includes some tests for converting both ways between
[
https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058575#comment-15058575
]
Dawid Weiss commented on LUCENE-6933:
-
Thanks Mark. I don't think I'll use automated
[
https://issues.apache.org/jira/browse/SOLR-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058549#comment-15058549
]
ASF subversion and git services commented on SOLR-8410:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke updated SOLR-8388:
--
Attachment: SOLR-8388-part3of2.patch
fix the {{ReturnFieldsTest.testToString}} test added
[
https://issues.apache.org/jira/browse/SOLR-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058567#comment-15058567
]
ASF subversion and git services commented on SOLR-8410:
---
Commit 17202
[
https://issues.apache.org/jira/browse/SOLR-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058557#comment-15058557
]
David Smiley commented on SOLR-3229:
[~hossman] HighlightComponent, DebugComponent, and
Let's just make some JIRA issues. I'm not worried about volunteers for any
of it yet, just a direction we agree upon. Once we know where we are going,
we generally don't have a big volunteer problem. We haven't heard from Uwe
yet, but really does seem like moving to Git makes the most sense.
I'm c
[
https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058546#comment-15058546
]
Mark Miller commented on LUCENE-6933:
-
For some reference, here is a wiki page managi
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5474/
Java: 32bit/jdk1.8.0_66 -client -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.core.TestDynamicLoading.testDynamicLoading
Error Message:
Could not get expected value 'X val changed' for path 'x' full output: {
"respo
If Dawid is volunteering to sort out this mess, +1 to let him make it
a move to git. I don't care if we disagree about JARs, I trust he will
do a good job and that is more important.
On Tue, Dec 15, 2015 at 12:44 PM, Dawid Weiss wrote:
>
> It's not true that nobody is working on this. I have been
Dawid Weiss created LUCENE-6933:
---
Summary: Create a (cleaned up) SVN history in git
Key: LUCENE-6933
URL: https://issues.apache.org/jira/browse/LUCENE-6933
Project: Lucene - Core
Issue Type: Ta
[
https://issues.apache.org/jira/browse/SOLR-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Molloy updated SOLR-8393:
---
Attachment: SOLR-8393.patch
Fix disappearing collections when using collection param (should not be abl
I know that, but I meant historical checkouts -- and if you add fake files
you're altering history :)
D.
On Tue, Dec 15, 2015 at 7:24 PM, Mike Drob wrote:
> 3 is typically solved by adding a .gitignore or .gitkeep file in what
> would be an empty directory, if the directory itself is important.
3 is typically solved by adding a .gitignore or .gitkeep file in what would
be an empty directory, if the directory itself is important.
On Tue, Dec 15, 2015 at 12:21 PM, Dawid Weiss wrote:
>
> Oh, just for completeness -- moving to git is not just about the version
> management, it's also:
>
>
Oh, just for completeness -- moving to git is not just about the version
management, it's also:
1) all the scripts that currently do validations, etc.
2) what to do with svn:* properties
3) what to do with empty folders (not available in git).
I don't volunteer to solve these :)
Dawid
On Tue,
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058463#comment-15058463
]
Steve Rowe commented on SOLR-7730:
--
bq. attaching SOLR-7730-changes.patch move it from 5.3
Ok, give me some time and I'll see what I can achieve. Now that I actually
wrote an SVN dump parser (validator and serializer) things are under much
better control...
I'll try to achieve the following:
1) selectively drop unnecessary stuff from history (cms/, javadocs/, JARs
and perhaps other bin
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-7730:
---
Attachment: SOLR-7730-changes.patch
attaching [^SOLR-7730-changes.patch] move it from 5.3 to 5.
[
https://issues.apache.org/jira/browse/SOLR-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev reopened SOLR-7730:
> speed-up faceting on doc values fields
> --
>
>
It's not true that nobody is working on this. I have been working on the
SVN dump in the meantime. You would not believe how incredibly complex the
process of processing that (remote) dump is. Let me highlight a few key
issues:
1) There is no "one" Lucene SVN repository that can be transferred to
[
https://issues.apache.org/jira/browse/SOLR-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-8372:
---
Attachment: SOLR-8372.patch
Here's a patch that allows bufferUpdates() to be called more than once, and
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14913/
Java: 32bit/jdk1.7.0_80 -client -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.search.ReturnFieldsTest.testToString
Error Message:
expected:<...s=(globs=[],fields=[[score, test, id],okFieldNames=[null, score,
test], id
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/259/
Java: multiarch/jdk1.7.0 -d32 -client -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.search.ReturnFieldsTest.testToString
Error Message:
expected:<...s=(globs=[],fields=[[score, test, id],okFieldNames=[null, scor
If we move to git, stripping out jars seems to be an independent decision?
Can you even strip out jars and preserve history (i.e. not change
hashes and invalidate everyone's forks/clones)?
I did run across this:
http://stackoverflow.com/questions/17470780/is-it-possible-to-slim-a-git-repository-wit
And if nobody steps up and "solves" the current technical issue will that
simply accelerate the (desired) shift to using git as the main repo for
future Lucene/Solr development? Would there be any downside to that outcome?
Is there any formal Apache policy for new projects as to whether they can
u
Let's just move to git. It's almost 2016. I suspect many contributors are
probably primarily working off the github mirror anyway. Is there any
great argument for delaying?
On Dec 15, 2015 11:51 AM, "Mark Miller" wrote:
> I don't think you will get a volunteer until someone sums up the
> discuss
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke reopened SOLR-8388:
---
> TestSolrQueryResponse (factor out, then extend)
> ---
I don't think you will get a volunteer until someone sums up the discussion
with a proposal that someone is not going to veto or something. We can't
expect everyone to read the same tea leaves and come to the same
conclusion.
Perhaps a stripped down mirror is the consensus. I'd rather we had some
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058305#comment-15058305
]
Christine Poerschke commented on SOLR-8388:
---
Thanks Steve. Looking into.
> TestS
I thought the general consensus at minimum was to investigate a git mirror
that stripped some artifacts out (jars etc) to lighten up the work of the
process. If at some point the project switched to git, such a mirror might
be a suitable git repo for the project with archived older versions in SVN.
Anyone willing to lead this discussion to some kind of better resolution?
Did that whole back and forth help with any ideas on the best path forward?
I know it's a complicated issue, git / svn, the light side, the dark side,
but doesn't GitHub also depend on this mirroring? It's going to be super
a
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058262#comment-15058262
]
Steve Rowe commented on SOLR-8388:
--
My Jenkins found a reproducible ReturnsFieldsTest.test
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15210/
Java: 64bit/jdk-9-ea+95 -XX:+UseCompressedOops -XX:+UseG1GC -XX:-CompactStrings
1 tests failed.
FAILED: org.apache.solr.cloud.HttpPartitionTest.test
Error Message:
Timeout occured while waiting response from server at:
http://
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/261/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC
4 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestCoreDiscovery
Error Message:
ERROR: SolrIndexSearcher opens=27 closes=26
Stack Trace:
java
[
https://issues.apache.org/jira/browse/SOLR-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Wille updated SOLR-8418:
-
Attachment: SOLR-8418.patch
> BoostQuery cannot be cast to TermQuery
>
[
https://issues.apache.org/jira/browse/SOLR-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058234#comment-15058234
]
Jens Wille commented on SOLR-8418:
--
I've attached a patch that fixes the issue for all thr
Jens Wille created SOLR-8418:
Summary: BoostQuery cannot be cast to TermQuery
Key: SOLR-8418
URL: https://issues.apache.org/jira/browse/SOLR-8418
Project: Solr
Issue Type: Bug
Component
[
https://issues.apache.org/jira/browse/LUCENE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058198#comment-15058198
]
Stéphane Campinas edited comment on LUCENE-6932 at 12/15/15 3:23 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Campinas updated LUCENE-6932:
--
Attachment: issue6932.patch
A possible solution
> Seek past EOF with RAMDirectory shou
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke resolved SOLR-8388.
---
Resolution: Fixed
> TestSolrQueryResponse (factor out, then extend)
> -
[
https://issues.apache.org/jira/browse/SOLR-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058195#comment-15058195
]
ASF subversion and git services commented on SOLR-8388:
---
Commit 17201
https://issues.apache.org/jira/browse/LUCENE-6932
On 15 December 2015 at 15:03, Robert Muir wrote:
> at a glance, this looks like a bug in RAMDirectory to me. Can you open an
> issue?
>
> On Tue, Dec 15, 2015 at 9:52 AM, Stéphane Campinas
> wrote:
> > Hi,
> >
> > In the JUnit test case from the
[
https://issues.apache.org/jira/browse/LUCENE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Campinas updated LUCENE-6932:
--
Attachment: testcase.txt
> Seek past EOF with RAMDirectory should throw EOFException
>
Stéphane Campinas created LUCENE-6932:
-
Summary: Seek past EOF with RAMDirectory should throw EOFException
Key: LUCENE-6932
URL: https://issues.apache.org/jira/browse/LUCENE-6932
Project: Lucene -
at a glance, this looks like a bug in RAMDirectory to me. Can you open an issue?
On Tue, Dec 15, 2015 at 9:52 AM, Stéphane Campinas
wrote:
> Hi,
>
> In the JUnit test case from the attached file, I call "IndexInput.seek()" on
> a position past
> EOF. However, there is no EOFException that is thr
1 - 100 of 126 matches
Mail list logo
