Re: Why no composite primary-key in lucene ?

@Erick, I kinda have to learn somehow. And I like to do performance optimizations. So learning + fun + performance .. yeah. Other projects that I want to do are harder (our email-exchange, my other threads on the list) so I have to start on something simpler. Example: I have a project where `id`

[jira] [Updated] (SOLR-9867) The Solr examples can not always be started after being stopped due to race with loading core.

[ https://issues.apache.org/jira/browse/SOLR-9867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-9867: - Attachment: SOLR-9867.patch Fixed some indentation issues, but otherwise identical. FWIW, I'm

[jira] [Commented] (SOLR-10519) SolrCLI.atPath cannot handle children that begin with a slash.

[ https://issues.apache.org/jira/browse/SOLR-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990124#comment-15990124 ] Erick Erickson commented on SOLR-10519: --- Unless anyone objects, I'm going to commit this probably

[jira] [Commented] (SOLR-7041) Remove defaultSearchField and solrQueryParser from schema

[ https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990114#comment-15990114 ] Pradeep commented on SOLR-7041: --- Bad. removing defaultOperator and defaultSearchField is bad idea. > Remove

[jira] [Commented] (SOLR-1485) Payload scoring support

[ https://issues.apache.org/jira/browse/SOLR-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990103#comment-15990103 ] Erik Hatcher commented on SOLR-1485: I've now committed/pushed everything to the branch needed for the

[jira] [Commented] (SOLR-1485) Payload scoring support

[ https://issues.apache.org/jira/browse/SOLR-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990095#comment-15990095 ] Erik Hatcher commented on SOLR-1485: I've started committing to branch jira/SOLR-1485:

[jira] [Updated] (SOLR-10586) Ban defaultOperator in schema for luceneMatchVersion =>6.6.0

[ https://issues.apache.org/jira/browse/SOLR-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-10586: --- Attachment: SOLR-10586.patch Patch for branch_6x. Will commit shortly, and then followup to remove

[jira] [Updated] (SOLR-10586) Ban defaultOperator in schema for luceneMatchVersion =>6.6.0

[ https://issues.apache.org/jira/browse/SOLR-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-10586: --- Description: Sub task of SOLR-7041. For new configs with luceneMatchVersion >=6.6.0 we'll throw an

[JENKINS] Lucene-Solr-master-Windows (64bit/jdk1.8.0_121) - Build # 6534 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6534/ Java: 64bit/jdk1.8.0_121 -XX:+UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SolrCloudExampleTest Error Message: ObjectTracker found 5 object(s) that were not

[jira] [Assigned] (SOLR-10586) Ban defaultOperator in schema for luceneMatchVersion =>6.6.0

[ https://issues.apache.org/jira/browse/SOLR-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl reassigned SOLR-10586: -- Assignee: Jan Høydahl > Ban defaultOperator in schema for luceneMatchVersion =>6.6.0 >

Re: Release 6.6

Martin - Interesting test but I couldn’t copy/paste it in to try it out as it uses some logging and APIs that aren’t already in the project and classpath of these lucene tests within that queries module (within IntelliJ, mind you). I was able to resolve the misunderstanding (and

[jira] [Updated] (SOLR-7041) Remove defaultSearchField and solrQueryParser from schema

[ https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Hatcher updated SOLR-7041: --- Summary: Remove defaultSearchField and solrQueryParser from schema (was: Nuke defaultSearchField and

[jira] [Created] (SOLR-10587) Ban defaultSearchField in schema for luceneMatchVersion =>6.6.0

Jan Høydahl created SOLR-10587: -- Summary: Ban defaultSearchField in schema for luceneMatchVersion =>6.6.0 Key: SOLR-10587 URL: https://issues.apache.org/jira/browse/SOLR-10587 Project: Solr

[jira] [Commented] (SOLR-7041) Nuke defaultSearchField and solrQueryParser from schema

[ https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990071#comment-15990071 ] Jan Høydahl commented on SOLR-7041: --- Further work will happen in the sub tasks, to split the elephant a

[jira] [Created] (SOLR-10586) Ban defaultOperator in schema for luceneMatchVersion =>6.6.0

Jan Høydahl created SOLR-10586: -- Summary: Ban defaultOperator in schema for luceneMatchVersion =>6.6.0 Key: SOLR-10586 URL: https://issues.apache.org/jira/browse/SOLR-10586 Project: Solr Issue

[jira] [Created] (SOLR-10585) Remove defaultSearchField completely in 7.0

Jan Høydahl created SOLR-10585: -- Summary: Remove defaultSearchField completely in 7.0 Key: SOLR-10585 URL: https://issues.apache.org/jira/browse/SOLR-10585 Project: Solr Issue Type: Sub-task

[jira] [Created] (SOLR-10584) Remove defaultOperator completely in 7.0

Jan Høydahl created SOLR-10584: -- Summary: Remove defaultOperator completely in 7.0 Key: SOLR-10584 URL: https://issues.apache.org/jira/browse/SOLR-10584 Project: Solr Issue Type: Sub-task

[jira] [Commented] (SOLR-7041) Nuke defaultSearchField and solrQueryParser from schema

[ https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990064#comment-15990064 ] ASF subversion and git services commented on SOLR-7041: --- Commit

[jira] [Updated] (SOLR-9867) The Solr examples can not always be started after being stopped due to race with loading core.

[ https://issues.apache.org/jira/browse/SOLR-9867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-9867: --- Attachment: SOLR-9867.patch [^SOLR-9867.patch] is on 6x. It enables

[jira] [Updated] (LUCENE-7810) false positive equality: distinctly diff join queries return equals()==true

[ https://issues.apache.org/jira/browse/LUCENE-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated LUCENE-7810: - Description: While working on SOLR-10583 I was getting some odd test failures that seemed to suggest we

Re: Why no composite primary-key in lucene ?

What you haven't really explained is why you care. The only hint I see is that you don't want to store the redundant data of your composite key as both individual fields and a concatenated . This feels like a whole lot of effort for no particularly good reason. Unless you have a bazillion _very_

[jira] [Resolved] (LUCENE-7798) add equals/hashCode to ToParentBlockJoinSortField

[ https://issues.apache.org/jira/browse/LUCENE-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev resolved LUCENE-7798. -- Resolution: Fixed Fix Version/s: 6.6 master (7.0) > add

[jira] [Resolved] (SOLR-10521) sort by string field of the nested child when searching with {!parent}

[ https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev resolved SOLR-10521. - Resolution: Fixed Fix Version/s: master (7.0) 6.6 > sort by

[jira] [Commented] (SOLR-7041) Nuke defaultSearchField and solrQueryParser from schema

[ https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990006#comment-15990006 ] ASF subversion and git services commented on SOLR-7041: --- Commit

Re: Why no composite primary-key in lucene ?

@Yonik Thanks, makes sense. @Walter After reading the cwiki page on update request processor looks like you can't modify the GET/DELETE handlers, right ? Because I want to NOT index/store the 'id' field, so

Re: Why no composite primary-key in lucene ?

If you do want a composite key in Solr, you could use an update request processor script to make it out of the multiple fields. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Apr 29, 2017, at 11:02 AM, Yonik Seeley wrote: > >

Re: Why no composite primary-key in lucene ?

On Sat, Apr 29, 2017 at 1:45 PM, Dorian Hoxha wrote: > @Yonik > > Thanks makes sense. So this means that the 'id' need to be indexed(is > always?), (so you can get/update/delete docs not in translog), right ? In Solr, yes. In Lucene, only if you want lookup-by-id to be

Re: Why no composite primary-key in lucene ?

@Yonik Thanks makes sense. So this means that the 'id' need to be indexed(is always?), (so you can get/update/delete docs not in translog), right ? On Sat, Apr 29, 2017 at 7:24 PM, Yonik Seeley wrote: > Solr doesn't use Lucene for RT GET, it uses it's transaction log. >

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3976 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3976/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SolrCloudExampleTest Error Message: ObjectTracker found 5 object(s) that were not released!!!

Re: Why no composite primary-key in lucene ?

Solr doesn't use Lucene for RT GET, it uses it's transaction log. Only when the document is not found in the transaction log will it go and consult the lucene index (which can only search as of the last commit). -Yonik On Sat, Apr 29, 2017 at 12:57 PM, Dorian Hoxha

Re: Why no composite primary-key in lucene ?

@Erick I know all that. My point is, lucene is NRT, while GET is RT (in both ES/SOLR). How does lucene return the right document (Term Query) before doing a commit on GET ? On Sat, Apr 29, 2017 at 6:48 PM, Erick Erickson wrote: > Internal magic. This is the point

[JENKINS] Lucene-Solr-master-Linux (64bit/jdk1.8.0_121) - Build # 19513 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19513/ Java: 64bit/jdk1.8.0_121 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.LeaderFailoverAfterPartitionTest.test Error Message: Expected 2 of 3 replicas to be active but only found 1;

Re: Why no composite primary-key in lucene ?

Internal magic. This is the point behind the admonitions against relying on the _internal_ Lucene doc ID for anything... it changes. For the same document. Even if the document doesn't change. Essentially when two segments are merged (and this is conceptual, not the code) all the live docs from

[JENKINS] Lucene-Solr-NightlyTests-master - Build # 1289 - Still unstable

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1289/ 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SolrCloudExampleTest Error Message: ObjectTracker found 5 object(s) that were not released!!! [RawDirectoryWrapper, MockDirectoryWrapper,

[jira] [Commented] (LUCENE-7514) TestLatLonPointQueries fails with biased (evil) numbers

[ https://issues.apache.org/jira/browse/LUCENE-7514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989906#comment-15989906 ] Dawid Weiss commented on LUCENE-7514: - Didn't look, but I once replaced float generation with

[JENKINS-EA] Lucene-Solr-master-Linux (32bit/jdk-9-ea+164) - Build # 19512 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19512/ Java: 32bit/jdk-9-ea+164 -server -XX:+UseParallelGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SolrCloudExampleTest Error Message: ObjectTracker found 5 object(s) that were not released!!!

[JENKINS] Lucene-Solr-master-Windows (32bit/jdk1.8.0_121) - Build # 6533 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6533/ Java: 32bit/jdk1.8.0_121 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testCollectionsAPI Error Message: expected:<3> but was:<1> Stack Trace:

[jira] [Commented] (LUCENE-7807) Test*RangeFieldQueries.testRandomBig() and .testRandomTiny() failures

[ https://issues.apache.org/jira/browse/LUCENE-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989878#comment-15989878 ] Steve Rowe commented on LUCENE-7807: ASF Jenkins found another reproducing seed for

Re: Release 6.6

Martin Gainty has shared a OneDrive file with you. To view it, click the link below. [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]

Re: Release 6.6

Martin - there is a test class specifically for this query. See the recent commits I've made to test it further fixing .equals/.hashCode and rewrite. Can you send your full test code? Erik > On Apr 29, 2017, at 07:32, Martin Gainty wrote: > > when Erik mentioned he

Re: Why no composite primary-key in lucene ?

Hi Shawn, ES has the same thing. You're right that no 'id' is needed when adding a document. But lucene has updateDocument: https://lucene.apache.org/core /6_4_0/core/org/apache/lucene/index/IndexWriter.html#updateD ocument-org.apache.lucene.index.Term-java.lang.Iterable- ? Or that doesn't need

[jira] [Updated] (LUCENE-7737) Remove spatial-extras dependency on queries

[ https://issues.apache.org/jira/browse/LUCENE-7737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-7737: - Fix Version/s: master (7.0) > Remove spatial-extras dependency on queries >

[jira] [Commented] (LUCENE-7741) Add explain() to DoubleValues

[ https://issues.apache.org/jira/browse/LUCENE-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989868#comment-15989868 ] David Smiley commented on LUCENE-7741: -- +1 looks great! * What is "NB " in the comments? *

[jira] [Commented] (LUCENE-7719) UnifiedHighlighter doesn't handle some AutomatonQuery's with multi-byte chars

[ https://issues.apache.org/jira/browse/LUCENE-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989866#comment-15989866 ] David Smiley commented on LUCENE-7719: -- [~mikemccand] What do you think of the patch? In

[jira] [Comment Edited] (LUCENE-7719) UnifiedHighlighter doesn't handle some AutomatonQuery's with multi-byte chars

[ https://issues.apache.org/jira/browse/LUCENE-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957326#comment-15957326 ] David Smiley edited comment on LUCENE-7719 at 4/29/17 12:19 PM: Here is a

[JENKINS] Lucene-Solr-Tests-master - Build # 1785 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1785/ 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SolrCloudExampleTest Error Message: ObjectTracker found 5 object(s) that were not released!!! [MockDirectoryWrapper, MDCAwareThreadPoolExecutor,

[jira] [Commented] (LUCENE-7798) add equals/hashCode to ToParentBlockJoinSortField

[ https://issues.apache.org/jira/browse/LUCENE-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989852#comment-15989852 ] ASF subversion and git services commented on LUCENE-7798: - Commit

Re: Release 6.6

when Erik mentioned he couldnt get SpanPayloadCheckQuery to work I was about to reply just run that TestCase (until i discovered there wasnt any!) i'll start the bidding at 1 dinar for TestCase org.apache.lucene.queries.payloads.TestPayloadCheckQuery mod: @org.junit.Test public void

[jira] [Commented] (LUCENE-7798) add equals/hashCode to ToParentBlockJoinSortField

[ https://issues.apache.org/jira/browse/LUCENE-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989847#comment-15989847 ] ASF subversion and git services commented on LUCENE-7798: - Commit

[JENKINS-EA] Lucene-Solr-master-Linux (32bit/jdk-9-ea+164) - Build # 19511 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19511/ Java: 32bit/jdk-9-ea+164 -client -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.handler.admin.MetricsHandlerTest.testPropertyFilter Error Message: Stack Trace: java.lang.AssertionError at

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 1272 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1272/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.update.AutoCommitTest.testMaxDocs Error Message: Exception during query Stack Trace: java.lang.RuntimeException:

[JENKINS] Lucene-Solr-NightlyTests-6.x - Build # 335 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.x/335/ 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.hdfs.HdfsRecoveryZkTest Error Message: ObjectTracker found 1 object(s) that were not released!!! [HdfsTransactionLog]

[JENKINS] Lucene-Solr-master-Linux (64bit/jdk1.8.0_121) - Build # 19510 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19510/ Java: 64bit/jdk1.8.0_121 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SolrCloudExampleTest Error Message: ObjectTracker found 5 object(s) that were not