Hoss Man created SOLR-13118:
---
Summary: Redesign integration tests for nodeAdded/nodeLost trigger
state restoration
Key: SOLR-13118
URL: https://issues.apache.org/jira/browse/SOLR-13118
Project: Solr
[
https://issues.apache.org/jira/browse/LUCENE-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734770#comment-16734770
]
David Smiley commented on LUCENE-8581:
--
I attached a patch about this.
> Change LatLonShape
[
https://issues.apache.org/jira/browse/LUCENE-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-8581:
-
Attachment: LUCENE-8581_bytes.patch
> Change LatLonShape encoding to use 4 BYTES Per Dimension
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Windows/941/
Java: 64bit/jdk1.8.0_172 -XX:+UseCompressedOops -XX:+UseG1GC
3 tests failed.
FAILED: org.apache.solr.cloud.OverseerRolesTest.testOverseerRole
Error Message:
Timed out waiting for overseer state change
Stack Trace:
On Fri, Jan 4, 2019 at 12:51 PM Shawn Heisey wrote:
> Looking at what came before, my preference would have been implicitly
> defined default types -- things like int, string, etc, defined in code.
> The only problem with that comes at Solr upgrade time ... what if we
> decide for a later
[
https://issues.apache.org/jira/browse/SOLR-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-13118:
---
Assignee: Hoss Man
Attachment: SOLR-13118.patch
In the attached patch, I've remedied this (in
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/7677/
Java: 64bit/jdk-11 -XX:-UseCompressedOops -XX:+UseParallelGC
6 tests failed.
FAILED: org.apache.solr.cloud.MissingSegmentRecoveryTest.testLeaderRecovery
Error Message:
Expected a collection with one shard and two replicas
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/1226/
No tests ran.
Build Log:
[...truncated 23486 lines...]
[asciidoctor:convert] asciidoctor: ERROR: about-this-guide.adoc: line 1:
invalid part, must have at least one section (e.g., chapter, appendix, etc.)
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-7.x/423/
2 tests failed.
FAILED: org.apache.solr.cloud.LIROnShardRestartTest.testAllReplicasInLIR
Error Message:
Path must not end with / character
Stack Trace:
java.lang.IllegalArgumentException: Path must not end with / character
[
https://issues.apache.org/jira/browse/SOLR-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734693#comment-16734693
]
Peter Williams commented on SOLR-12858:
---
I have (so far) been able to workaround this problem by
Build: https://builds.apache.org/job/Lucene-Solr-BadApples-Tests-master/253/
2 tests failed.
FAILED: org.apache.solr.cloud.MultiThreadedOCPTest.test
Error Message:
acoll: 1546651816076 bcoll: 1546651816235
Stack Trace:
java.lang.AssertionError: acoll: 1546651816076 bcoll: 1546651816235
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/23464/
Java: 64bit/jdk1.8.0_172 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED:
org.apache.solr.client.solrj.io.stream.MathExpressionTest.testGammaDistribution
Error Message:
0.8126481483629882
Richard O'Sullivan created SOLR-13117:
-
Summary: Present Introspect as WADL
Key: SOLR-13117
URL: https://issues.apache.org/jira/browse/SOLR-13117
Project: Solr
Issue Type: New Feature
Build:
https://builds.apache.org/job/Lucene-Solr-BadApples-NightlyTests-master/44/
22 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.cloud.RestartWhileUpdatingTest
Error Message:
ObjectTracker found 30 object(s) that were not released!!! [MMapDirectory,
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-11126:
Attachment: SOLR-11126.patch
> Node-level health check handler
> ---
>
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-11126:
Attachment: SOLR-11126.patch
> Node-level health check handler
> ---
>
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-11126:
Attachment: (was: SOLR-11126.patch)
> Node-level health check handler
>
[
https://issues.apache.org/jira/browse/LUCENE-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734103#comment-16734103
]
Michael McCandless commented on LUCENE-8601:
Thanks [~muralikpbhat] – I'll review and push
Build: https://builds.apache.org/job/Lucene-Solr-Tests-7.x/1186/
1 tests failed.
FAILED: org.apache.solr.core.TestDynamicLoading.testDynamicLoading
Error Message:
Could not get expected value
'org.apache.solr.core.BlobStoreTestRequestHandler' for path
'overlay/requestHandler/\/test1/class'
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1741/
1 tests failed.
FAILED: org.apache.solr.cloud.hdfs.StressHdfsTest.test
Error Message:
There are still nodes recoverying - waited for 330 seconds
Stack Trace:
java.lang.AssertionError: There are still nodes recoverying -
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734037#comment-16734037
]
Amrit Sarkar commented on SOLR-11126:
-
Ah :( Right. Didn't fail to start for me but yes fails to
[
https://issues.apache.org/jira/browse/LUCENE-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734046#comment-16734046
]
Murali Krishna P commented on LUCENE-8601:
--
Thanks [~mikemccand]. Uploaded a separate patch for
[
https://issues.apache.org/jira/browse/LUCENE-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734119#comment-16734119
]
David Smiley commented on LUCENE-8622:
--
Cool algorithms here.
Can you please rename
[
https://issues.apache.org/jira/browse/LUCENE-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734136#comment-16734136
]
Alan Woodward commented on LUCENE-8622:
---
Thanks for the review [~dsmiley]! Have updated the patch
[
https://issues.apache.org/jira/browse/LUCENE-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Krishna P updated LUCENE-8601:
-
Attachment: 7x_LUCENE-8601.06.patch
> Adding attributes to IndexFieldType
>
[
https://issues.apache.org/jira/browse/LUCENE-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734059#comment-16734059
]
Alan Woodward commented on LUCENE-8622:
---
New patch, bringing things up to date with master
> Add
[
https://issues.apache.org/jira/browse/LUCENE-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-8622:
--
Attachment: LUCENE-8622.patch
> Add a MinimumShouldMatch interval iterator
>
[
https://issues.apache.org/jira/browse/LUCENE-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-8622:
--
Attachment: LUCENE-8622.patch
> Add a MinimumShouldMatch interval iterator
>
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733991#comment-16733991
]
Shalin Shekhar Mangar commented on SOLR-11126:
--
[~sarkaramr...@gmail.com] -- Solr fails to
[
https://issues.apache.org/jira/browse/LUCENE-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-8629:
--
Attachment: LUCENE-8629.patch
> Add some more Interval functions
>
[
https://issues.apache.org/jira/browse/LUCENE-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733997#comment-16733997
]
Alan Woodward commented on LUCENE-8629:
---
Actual working patch attached this time...
> Add some
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733958#comment-16733958
]
Amrit Sarkar commented on SOLR-11126:
-
Thanks, Shalin, apologies you had to review multiple times. I
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-11126:
Attachment: SOLR-11126.patch
> Node-level health check handler
> ---
>
Alan Woodward created LUCENE-8629:
-
Summary: Add some more Interval functions
Key: LUCENE-8629
URL: https://issues.apache.org/jira/browse/LUCENE-8629
Project: Lucene - Core
Issue Type: Task
Hi Uwe & Dawid,
Happy New Year!
*OpenJDK builds *- JDK 12 Early Access build 26 is available at
http://jdk.java.net/12/
* These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733966#comment-16733966
]
Shalin Shekhar Mangar commented on SOLR-11126:
--
This is interesting. The system, thread,
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-7.x/422/
3 tests failed.
FAILED:
org.apache.lucene.search.join.TestBlockJoin.testMultiChildQueriesOfDiffParentLevels
Error Message:
CheckIndex failed
Stack Trace:
java.lang.RuntimeException: CheckIndex failed
at
[
https://issues.apache.org/jira/browse/LUCENE-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-8629:
--
Attachment: LUCENE-8629.patch
> Add some more Interval functions
>
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Linux/3340/
Java: 64bit/jdk-9.0.4 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 1966 lines...]
[junit4] JVM J1: stderr was not empty, see:
[
https://issues.apache.org/jira/browse/SOLR-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734225#comment-16734225
]
ASF subversion and git services commented on SOLR-13090:
Commit
First off, the field in question is "FileContent", why do you think
the filed "text" is the problem?
Try switching FileContent to a text-based type.
If that's not the case, depending on the tokenizer and the input you
_still_ may
have an immense term even if you have a text-based field. For
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/7676/
Java: 64bit/jdk-10.0.1 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 2096 lines...]
[junit4] JVM J1: stderr was not empty, see:
[
https://issues.apache.org/jira/browse/SOLR-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734221#comment-16734221
]
Jan Høydahl commented on SOLR-7896:
---
{quote}I'm confused about the last sentence there. I don't quite
[
https://issues.apache.org/jira/browse/SOLR-13116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734215#comment-16734215
]
Cassandra Targett commented on SOLR-13116:
--
The description for this issue isn't exactly
[
https://issues.apache.org/jira/browse/SOLR-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734209#comment-16734209
]
Cassandra Targett commented on SOLR-7896:
-
bq. If the user opens a page or attempts an action that
[
https://issues.apache.org/jira/browse/SOLR-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734209#comment-16734209
]
Cassandra Targett edited comment on SOLR-7896 at 1/4/19 2:49 PM:
-
bq. If
I'm perhaps slightly conservative with respect to configuration, but I'm
not fond of hidden configuration that I can't see. What I don't like is
looking at a config file and not seeing the full story. That means i have
to read the config and ALSO go read some part of the documentation that
I've
I'm thinking this feature would be used conservatively -- and thus just
primitive types that wouldn't have an interesting configuration to them, or
for something you are really not expected to change (the nest path of
nested docs). So you wouldn't feel you had to go read the docs. The
schema
[
https://issues.apache.org/jira/browse/SOLR-13116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734286#comment-16734286
]
Jan Høydahl commented on SOLR-13116:
I have not used Kerberos with Solr. How does this work today? Is
What about if a system schema was loaded at a startup implicitly.
Then, if a new schema is loaded and type definition is missing, it is
copied - at that time - into the specific schema. So, on the first
rewrite those - and only those used - types will be written out.
This allows to version the
[
https://issues.apache.org/jira/browse/LUCENE-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734391#comment-16734391
]
ASF subversion and git services commented on LUCENE-8601:
-
Commit
Github user jpountz commented on a diff in the pull request:
https://github.com/apache/lucene-solr/pull/525#discussion_r245364034
--- Diff:
lucene/core/src/java/org/apache/lucene/codecs/lucene80/IndexedDISI.java ---
@@ -0,0 +1,601 @@
+/*
+ * Licensed to the Apache Software
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Windows/940/
Java: 64bit/jdk-12-ea+23 -XX:-UseCompressedOops -XX:+UseParallelGC
2 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeWithPullReplicasTest.test
Error Message:
Test abandoned because suite timeout was reached.
[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734425#comment-16734425
]
Lucene/Solr QA commented on SOLR-11126:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote ||
I'm jumping into this conversation a little bit late. Sorry for any
problems that causes.
On 1/4/2019 9:52 AM, Alexandre Rafalovitch wrote:
What about if a system schema was loaded at a startup implicitly.
Then, if a new schema is loaded and type definition is missing, it is
copied - at that
[
https://issues.apache.org/jira/browse/SOLR-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-13114.
--
Resolution: Invalid
The vulnerability reported by the scanner is a false positive. It
[
https://issues.apache.org/jira/browse/SOLR-13115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-13115.
--
Resolution: Invalid
The vulnerability reported by the scanner is a false positive. It
[
https://issues.apache.org/jira/browse/SOLR-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-13109.
--
Resolution: Invalid
The vulnerability reported by the scanner is a false positive. It
[
https://issues.apache.org/jira/browse/SOLR-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-13113.
--
Resolution: Invalid
The vulnerability reported by the scanner is a false positive. It
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5002/
Java: 64bit/jdk-9 -XX:+UseCompressedOops -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 14003 lines...]
[junit4] JVM J0: stdout was not empty, see:
[
https://issues.apache.org/jira/browse/LUCENE-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734555#comment-16734555
]
Lucene/Solr QA commented on LUCENE-8601:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote ||
[
https://issues.apache.org/jira/browse/SOLR-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-13111.
--
Resolution: Invalid
The vulnerability reported by the scanner is a false positive. It
The PyLucene 7.6.0 (rc1) release tracking the recent release of
Apache Lucene 7.6.0 is ready.
A release candidate is available from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/7.6.0-rc1/
PyLucene 7.6.0 is built with JCC 3.4 included in these release artifacts.
JCC 3.4 supports
63 matches
Mail list logo