[jira] [Commented] (LUCENE-5205) SpanQueryParser with recursion, analysis and syntax very similar to classic QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734335#comment-14734335 ] Modassar Ather commented on LUCENE-5205: Hi [~talli...@mitre.org] There is a document with

[jira] [Updated] (LUCENE-6783) FuzzyLikeThisQuery.rewrite should not have side effects

[ https://issues.apache.org/jira/browse/LUCENE-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-6783: - Attachment: LUCENE-6783.patch Here is a patch. > FuzzyLikeThisQuery.rewrite should not have

[jira] [Created] (LUCENE-6783) FuzzyLikeThisQuery.rewrite should not have side effects

Adrien Grand created LUCENE-6783: Summary: FuzzyLikeThisQuery.rewrite should not have side effects Key: LUCENE-6783 URL: https://issues.apache.org/jira/browse/LUCENE-6783 Project: Lucene - Core

Re: [JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.8.0_60) - Build # 13870 - Failure!

Looks like https://issues.apache.org/jira/browse/LUCENE-6629 (Jenkins jobs randomly hang and hit 7200 second timeout) ... I tested that repro line and it runs quickly for me. I'll update the issue... Mike McCandless http://blog.mikemccandless.com On Mon, Sep 7, 2015 at 4:57 PM, Policeman

[jira] [Commented] (LUCENE-6629) Random 7200 seconds build timeouts / infinite loops in Lucene tests?

[ https://issues.apache.org/jira/browse/LUCENE-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734503#comment-14734503 ] Michael McCandless commented on LUCENE-6629: Another one:

[jira] [Commented] (LUCENE-6783) FuzzyLikeThisQuery.rewrite should not have side effects

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

[jira] [Commented] (LUCENE-6773) Always flatten nested conjunctions

[ https://issues.apache.org/jira/browse/LUCENE-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734291#comment-14734291 ] Ryan Ernst commented on LUCENE-6773: +1 Can you add a test to TestConjunctionDISI? > Always flatten

[jira] [Commented] (LUCENE-6590) Explore different ways to apply boosts

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

[jira] [Updated] (LUCENE-6758) Adding a SHOULD clause to a BQ over an empty field clears the score when using DefaultSimilarity

[ https://issues.apache.org/jira/browse/LUCENE-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-6758: Attachment: LUCENE-6758.patch The problem is just with crappy queryNorm in DefaultSimilarity, as

[jira] [Updated] (SOLR-7569) Create an API to force a leader election between nodes

[ https://issues.apache.org/jira/browse/SOLR-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Chattopadhyaya updated SOLR-7569: --- Attachment: SOLR-7569.patch * Passing the async parameter through, * Tests now

[jira] [Created] (SOLR-8018) NPE if distrib=true on single node set up

Markus Jelsma created SOLR-8018: --- Summary: NPE if distrib=true on single node set up Key: SOLR-8018 URL: https://issues.apache.org/jira/browse/SOLR-8018 Project: Solr Issue Type: Bug

[jira] [Commented] (LUCENE-6758) Adding a SHOULD clause to a BQ over an empty field clears the score when using DefaultSimilarity

[ https://issues.apache.org/jira/browse/LUCENE-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734713#comment-14734713 ] Adrien Grand commented on LUCENE-6758: -- +1 > Adding a SHOULD clause to a BQ over an empty field

[jira] [Created] (LUCENE-6784) Enable query caching by default

Adrien Grand created LUCENE-6784: Summary: Enable query caching by default Key: LUCENE-6784 URL: https://issues.apache.org/jira/browse/LUCENE-6784 Project: Lucene - Core Issue Type:

[jira] [Commented] (LUCENE-6783) FuzzyLikeThisQuery.rewrite should not have side effects

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

[jira] [Commented] (LUCENE-6590) Explore different ways to apply boosts

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

[jira] [Resolved] (LUCENE-6783) FuzzyLikeThisQuery.rewrite should not have side effects

[ https://issues.apache.org/jira/browse/LUCENE-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand resolved LUCENE-6783. -- Resolution: Fixed > FuzzyLikeThisQuery.rewrite should not have side effects >

[jira] [Resolved] (LUCENE-6590) Explore different ways to apply boosts

[ https://issues.apache.org/jira/browse/LUCENE-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand resolved LUCENE-6590. -- Resolution: Fixed Fix Version/s: 5.4 > Explore different ways to apply boosts >

Re: [CI] Lucene 5x Linux 64 Test Only - Build # 62917 - Failure!

Looks like https://issues.apache.org/jira/browse/LUCENE-6629 again (tests randomly, inexplicably timeout at 7200 seconds)... when I run the repro line, the test runs quickly ... so weird ... I'll update the issue. Mike McCandless On Tue, Sep 8, 2015 at 12:21 AM, wrote: >

[jira] [Created] (SOLR-8017) solr.PointType can't deal with coordination in format like (0.9504547, 1.0, 1.0890503)

wangshanshan created SOLR-8017: -- Summary: solr.PointType can't deal with coordination in format like (0.9504547, 1.0, 1.0890503) Key: SOLR-8017 URL: https://issues.apache.org/jira/browse/SOLR-8017

[JENKINS] Lucene-Solr-NightlyTests-trunk - Build # 789 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/789/ 2 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: Error from server at http://127.0.0.1:55860/qm_qk/q: Could not load collection from ZK:halfcollectionblocker Stack Trace:

[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0_60) - Build # 14157 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/14157/ Java: 32bit/jdk1.8.0_60 -server -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.TestRandomRequestDistribution.testRequestTracking Error Message: Shard a1x2_shard1_replica2 received all 10 requests Stack

[jira] [Commented] (LUCENE-6629) Random 7200 seconds build timeouts / infinite loops in Lucene tests?

[ https://issues.apache.org/jira/browse/LUCENE-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734549#comment-14734549 ] Michael McCandless commented on LUCENE-6629: Another one:

[jira] [Updated] (LUCENE-6784) Enable query caching by default

[ https://issues.apache.org/jira/browse/LUCENE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-6784: - Attachment: LUCENE-6784.patch Here is a patch. The default cache has a size of 32MB and I added

[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0_60) - Build # 14156 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/14156/ Java: 32bit/jdk1.8.0_60 -client -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.CdcrReplicationHandlerTest.doTest Error Message: Index: 0, Size: 0 Stack Trace: java.lang.IndexOutOfBoundsException: Index:

[jira] [Closed] (LUCENE-6369) Make queries more defensive and clone deeply

[ https://issues.apache.org/jira/browse/LUCENE-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand closed LUCENE-6369. Resolution: Won't Fix Fix Version/s: (was: 5.2) (was: Trunk)

[jira] [Updated] (SOLR-7819) ZkController.ensureReplicaInLeaderInitiatedRecovery does not respect retryOnConnLoss

[ https://issues.apache.org/jira/browse/SOLR-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-7819: Attachment: SOLR-7819.patch # Adds a new test: TestLeaderInitiatedRecoveryThread #

[jira] [Created] (LUCENE-6787) BooleanQuery should be able to drop duplicate non-scoring clauses

Terry Smith created LUCENE-6787: --- Summary: BooleanQuery should be able to drop duplicate non-scoring clauses Key: LUCENE-6787 URL: https://issues.apache.org/jira/browse/LUCENE-6787 Project: Lucene -

[jira] [Updated] (LUCENE-6679) Filter's Weight.explain returns an explanation with isMatch==true even on documents that don't match

[ https://issues.apache.org/jira/browse/LUCENE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terry Smith updated LUCENE-6679: Attachment: LUCENE-6679.patch Here is a patch (against trunk) that adds test coverage for

[jira] [Commented] (SOLR-7990) timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits

[ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735415#comment-14735415 ] Yonik Seeley commented on SOLR-7990: OK, I figured out why your test was failing... there were no

[jira] [Updated] (LUCENE-6787) BooleanQuery should be able to drop duplicate non-scoring clauses

[ https://issues.apache.org/jira/browse/LUCENE-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terry Smith updated LUCENE-6787: Attachment: LUCENE-6787.patch Here is a patch based on [~jpountz]'s suggestion of putting this

[jira] [Commented] (LUCENE-6773) Always flatten nested conjunctions

[ https://issues.apache.org/jira/browse/LUCENE-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735508#comment-14735508 ] Ryan Ernst commented on LUCENE-6773: Test looks good, thanks! > Always flatten nested conjunctions >

[JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 15 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.3/15/ No tests ran. Build Log: [...truncated 53053 lines...] prepare-release-no-sign: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.3/lucene/build/smokeTestRelease/dist [copy] Copying

[jira] [Updated] (SOLR-7990) timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits

[ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-7990: --- Attachment: SOLR-7990.patch Here's the latest patch with the rewritten ExitableDirectoryReaderTest.

[jira] [Commented] (LUCENE-5205) SpanQueryParser with recursion, analysis and syntax very similar to classic QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735398#comment-14735398 ] David Smiley commented on LUCENE-5205: -- Can you please output what the output is now and what you

[JENKINS] Lucene-Solr-Tests-trunk-Java8 - Build # 377 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/377/ 1 tests failed. REGRESSION: org.apache.solr.cloud.DistribCursorPagingTest.test Error Message: expected:<1264> but was:<902> Stack Trace: java.lang.AssertionError: expected:<1264> but was:<902> at

[jira] [Updated] (LUCENE-5503) Trivial fixes to WeightedSpanTermExtractor

[ https://issues.apache.org/jira/browse/LUCENE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-5503: - Assignee: David Smiley I'll take a look at this by next week. > Trivial fixes to

[jira] [Commented] (LUCENE-6787) BooleanQuery should be able to drop duplicate non-scoring clauses

[ https://issues.apache.org/jira/browse/LUCENE-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735625#comment-14735625 ] Adrien Grand commented on LUCENE-6787: -- The patch looks good to me. Maybe we could just create the

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Description: The problem is that Solr 4.10.3,

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Description: The problem is that Solr 4.10.3,

[jira] [Commented] (SOLR-7613) solrcore.properties file should be loaded if it resides in ZooKeeper

[ https://issues.apache.org/jira/browse/SOLR-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735665#comment-14735665 ] Steve Davids commented on SOLR-7613: I went ahead and swapped our {{solrcore.properties}} over to

[jira] [Commented] (SOLR-7990) timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits

[ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735666#comment-14735666 ] Yonik Seeley commented on SOLR-7990: I'm working on test fixes... my test changes were no good since

[jira] [Commented] (SOLR-6974) Rare DistribCursorPagingTest fail.

[ https://issues.apache.org/jira/browse/SOLR-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735601#comment-14735601 ] Steve Rowe commented on SOLR-6974: -- Yet another, different, fail on ASF Jenkins

[jira] [Commented] (LUCENE-6305) BooleanQuery.equals should ignore clause order

[ https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735615#comment-14735615 ] Adrien Grand commented on LUCENE-6305: -- Actually I think of this change more as a bug fix than as an

[jira] [Commented] (SOLR-7435) NPE in FieldCollapsingQParser

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735614#comment-14735614 ] Joel Bernstein commented on SOLR-7435: -- I went back and reviewed the CollapsingQParserPlugin based on

[jira] [Comment Edited] (SOLR-7990) timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits

[ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735628#comment-14735628 ] Erick Erickson edited comment on SOLR-7990 at 9/8/15 9:17 PM: -- Seems I'm the

[jira] [Updated] (LUCENE-6785) Consider merging Query.rewrite() into Query.createWeight()

[ https://issues.apache.org/jira/browse/LUCENE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward updated LUCENE-6785: -- Attachment: LUCENE-6785.patch Here's a first-pass patch, just changing things in lucene-core.

[jira] [Commented] (SOLR-7990) timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits

[ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735628#comment-14735628 ] Erick Erickson commented on SOLR-7990: -- Seems I'm the pigeon more often than the statue lately

[jira] [Commented] (SOLR-8016) CloudSolrClient has extremely verbose error logging

[ https://issues.apache.org/jira/browse/SOLR-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735752#comment-14735752 ] Greg Pendlebury commented on SOLR-8016: --- Lowering the level to INFO would be good in our case,

[jira] [Commented] (LUCENE-6785) Consider merging Query.rewrite() into Query.createWeight()

[ https://issues.apache.org/jira/browse/LUCENE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735655#comment-14735655 ] Robert Muir commented on LUCENE-6785: - I didn't thoroughly examine the patch, but this part alone is

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Fix Version/s: (was: 5.2) 5.4 > NPE can occur if CollapsingQParserPlugin is

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Affects Version/s: 4.8.1 4.9.1 4.10.1

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Description: The problem is that Solr 4.10.3,

[jira] [Resolved] (SOLR-7775) support SolrCloud collection as fromIndex param in query-time join

[ https://issues.apache.org/jira/browse/SOLR-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev resolved SOLR-7775. Resolution: Fixed updated ref guide

[jira] [Commented] (SOLR-6549) bin/solr script should support a -s option to set the -Dsolr.solr.home property

[ https://issues.apache.org/jira/browse/SOLR-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735640#comment-14735640 ] Shawn Heisey commented on SOLR-6549: [~dragonsinth] popped up on IRC asking about GC tuning options,

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Description: The problem is that

[jira] [Updated] (SOLR-7435) NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-7435: - Summary: NPE can occur if CollapsingQParserPlugin is used two or more times in the same query

[jira] [Commented] (SOLR-7929) SimplePostTool (also bin/post) -filetypes "*" does not work properly in 'web' mode

[ https://issues.apache.org/jira/browse/SOLR-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735662#comment-14735662 ] Erik Hatcher commented on SOLR-7929: The commits were not SOLR-7929 prefixed, so they didn't get added

[jira] [Comment Edited] (SOLR-7929) SimplePostTool (also bin/post) -filetypes "*" does not work properly in 'web' mode

[ https://issues.apache.org/jira/browse/SOLR-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735662#comment-14735662 ] Erik Hatcher edited comment on SOLR-7929 at 9/8/15 9:35 PM: The commits were

[jira] [Commented] (LUCENE-6784) Enable query caching by default

[ https://issues.apache.org/jira/browse/LUCENE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734772#comment-14734772 ] Adrien Grand commented on LUCENE-6784: -- Test cases can't make use of this default query cache anyway

[jira] [Created] (SOLR-8019) OpenBitSet.class missing in Lucene core 5

Thomas Meyer created SOLR-8019: -- Summary: OpenBitSet.class missing in Lucene core 5 Key: SOLR-8019 URL: https://issues.apache.org/jira/browse/SOLR-8019 Project: Solr Issue Type: Bug Affects

[jira] [Closed] (SOLR-8019) OpenBitSet.class missing in Lucene core 5

[ https://issues.apache.org/jira/browse/SOLR-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev closed SOLR-8019. -- Resolution: Won't Fix OpenBitSet was removed in Lucene 5 see

[JENKINS] Lucene-Solr-Tests-trunk-Java8 - Build # 376 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/376/ 1 tests failed. REGRESSION: org.apache.solr.cloud.OverseerTest.testExternalClusterStateChangeBehavior Error Message: Illegal state, was: down expected:active clusterState:live nodes:[]collections:{c1=DocCollection(c1)={

[jira] [Commented] (LUCENE-6650) Remove dependency of lucene/spatial on oal.search.Filter

[ https://issues.apache.org/jira/browse/LUCENE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734859#comment-14734859 ] Adrien Grand commented on LUCENE-6650: -- David, do you think you will have time to work on this again

[jira] [Commented] (LUCENE-6758) Adding a SHOULD clause to a BQ over an empty field clears the score when using DefaultSimilarity

[ https://issues.apache.org/jira/browse/LUCENE-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734875#comment-14734875 ] Robert Muir commented on LUCENE-6758: - Thank you for contributing the tests. > Adding a SHOULD

[jira] [Updated] (LUCENE-6774) Remove solr hack in MorfologikFilter

[ https://issues.apache.org/jira/browse/LUCENE-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-6774: -- Fix Version/s: 5.3.1 > Remove solr hack in MorfologikFilter >

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 3512 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3512/ 1 tests failed. REGRESSION: org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication Error Message: Index: 0, Size: 0 Stack Trace: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

Re: 5.3.1 bug fix release

I would like to start the process ASAP. I volunteer to be the RM. Please let me know the list of tickets you would like to include in the release and we can coordinate the rest On Sep 8, 2015 2:32 AM, "Shawn Heisey" wrote: > On 9/5/2015 10:43 PM, Shalin Shekhar Mangar

[jira] [Commented] (LUCENE-6305) BooleanQuery.equals should ignore clause order

[ https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734785#comment-14734785 ] Adrien Grand commented on LUCENE-6305: -- bq. Slightly off topic to your original goal, but what do

RE: 5.3.1 bug fix release

The Morphologik stuff should be backported: https://issues.apache.org/jira/browse/LUCENE-6774 This breaks Non-Solr apps. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de

[jira] [Commented] (LUCENE-6758) Adding a SHOULD clause to a BQ over an empty field clears the score when using DefaultSimilarity

[ https://issues.apache.org/jira/browse/LUCENE-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734796#comment-14734796 ] Terry Smith commented on LUCENE-6758: - Ah, you've changed DefaultSimilarity.idf() to use (docCount +

[jira] [Updated] (LUCENE-6305) BooleanQuery.equals should ignore clause order

[ https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-6305: - Attachment: LUCENE-6305.patch Revisiting this issue now that queries can be considered

[jira] [Commented] (LUCENE-6784) Enable query caching by default

[ https://issues.apache.org/jira/browse/LUCENE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734768#comment-14734768 ] Robert Muir commented on LUCENE-6784: - I'm a little concerned since tests run with 512MB heap (except

[jira] [Reopened] (LUCENE-6774) Remove solr hack in MorfologikFilter

[ https://issues.apache.org/jira/browse/LUCENE-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reopened LUCENE-6774: --- Reopen for backport > Remove solr hack in MorfologikFilter >

[jira] [Updated] (LUCENE-6773) Always flatten nested conjunctions

[ https://issues.apache.org/jira/browse/LUCENE-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-6773: - Attachment: LUCENE-6773.patch Thanks Ryan for having a look. Here is an updated patch. > Always

[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 272 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/272/ No tests ran. Build Log: [...truncated 12326 lines...] BUILD FAILED /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/build.xml:511: The following error occurred while executing this line:

Re: Encrypted index?

> > bq: I was rather hoping that I could do the encryption and subsequent > decryption at a level below the search itself > I am not sure what "bq" standard for? Aside from the different encryption key per index (or whatever), why > does the client think this is any more secure than an

[jira] [Commented] (SOLR-8016) CloudSolrClient has extremely verbose error logging

[ https://issues.apache.org/jira/browse/SOLR-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735827#comment-14735827 ] Mark Miller commented on SOLR-8016: --- Pretty sure CloudSolrClient should not be retrying on such errors.

[jira] [Updated] (SOLR-7990) timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits

[ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-7990: --- Attachment: SOLR-7990.patch Here's the final patch. I also incorporated parts of Erick's test and

Re: [CI] Lucene 5x Linux 64 Test Only - Build # 63025 - Failure!

I'll dig ... it repros on beasting. Separately, it looks like build failures from the ES jenkins instances still must go through moderation on the Lucene dev list? (I don't see this build failure on the dev list yet ...). We had tried to fix this but it looks like it did not take! Mike

[jira] [Commented] (SOLR-8016) CloudSolrClient has extremely verbose error logging

[ https://issues.apache.org/jira/browse/SOLR-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735798#comment-14735798 ] Mark Miller commented on SOLR-8016: --- That sounds like a different issue - the CloudSolrClient really

[jira] [Commented] (SOLR-8016) CloudSolrClient has extremely verbose error logging

[ https://issues.apache.org/jira/browse/SOLR-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735813#comment-14735813 ] Greg Pendlebury commented on SOLR-8016: --- I haven't looked at the innards of the method enough to say

Re: Encrypted index?

> The problem with encrypted file systems is that if someone gets access to > the file system (not the disk, the file system e.g via ssh), it is wide > open to it. It's like my work laptop's disk is encrypted, but after I've > entered my password, all files are readable to me. However, files that

[jira] [Created] (SOLR-8021) TestCSVResponseWriter.testPseudoFields failure

Steve Rowe created SOLR-8021: Summary: TestCSVResponseWriter.testPseudoFields failure Key: SOLR-8021 URL: https://issues.apache.org/jira/browse/SOLR-8021 Project: Solr Issue Type: Bug

Re: Encrypted index?

Thanks very much Jack, I will take a look into those. On 8 September 2015 at 16:21, Jack Krupansky wrote: > Here's an old Lucene issue/patch for an AES encrypted Lucene directory > class that might give you some ideas: >

[jira] [Commented] (SOLR-7978) Really fix the example/files update-script Java version issues

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

[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b78) - Build # 14163 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/14163/ Java: 64bit/jdk1.9.0-ea-b78 -XX:-UseCompressedOops -XX:+UseParallelGC 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SaslZkACLProviderTest Error Message: 5 threads leaked from SUITE scope at

Re: [CI] Lucene 5x Linux 64 Test Only - Build # 63025 - Failure!

I’m a dev list moderator, and I haven’t seen this message (yet?). I checked my Junk folder and it’s not there either (Gmail puts some email to be moderated there sometimes). AFAICT the email was sent at 17:40 EDT or so, but it’s been over two hours now. But yes every few days ES Jenkins

[jira] [Resolved] (LUCENE-6774) Remove solr hack in MorfologikFilter

[ https://issues.apache.org/jira/browse/LUCENE-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler resolved LUCENE-6774. --- Resolution: Fixed OK, I backported. > Remove solr hack in MorfologikFilter >

[jira] [Updated] (LUCENE-6650) Remove dependency of lucene/spatial on oal.search.Filter

[ https://issues.apache.org/jira/browse/LUCENE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-6650: - Attachment: LUCENE-6650.patch Hi Adrien. I'm attaching my patch in progress from when I last

[jira] [Commented] (LUCENE-6774) Remove solr hack in MorfologikFilter

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

[jira] [Commented] (LUCENE-6784) Enable query caching by default

[ https://issues.apache.org/jira/browse/LUCENE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734893#comment-14734893 ] Robert Muir commented on LUCENE-6784: - Thats true, I guess there is always the situation of

Re: Encrypted index?

> > I think you could probably add transparent encryption/decryption at the > Lucene level in a custom codec. That probably has implications for > being able to read the older index when it's time to upgrade Lucene, > with a complete reindex being the likely solution. Others will need to >

RE: 5.3.1 bug fix release

Hi, I also backported the Java 9 fix, so I can start the Jenkins test of 5.3 again. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de From: Noble Paul [mailto:noble.p...@gmail.com] Sent:

Re: Encrypted index?

Thanks Walter, that would be a neat solution if we just wanted to store values, but we also want full-text query capabilities. On 5 September 2015 at 17:56, Walter Underwood wrote: > Alternatively, do not store values in the Solr fields. Return a key and > fetch encrypted

[jira] [Commented] (LUCENE-6758) Adding a SHOULD clause to a BQ over an empty field clears the score when using DefaultSimilarity

[ https://issues.apache.org/jira/browse/LUCENE-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734978#comment-14734978 ] Michael McCandless commented on LUCENE-6758: +1 > Adding a SHOULD clause to a BQ over an

[jira] [Comment Edited] (LUCENE-5205) SpanQueryParser with recursion, analysis and syntax very similar to classic QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734997#comment-14734997 ] Tim Allison edited comment on LUCENE-5205 at 9/8/15 3:34 PM: - This looks like

[jira] [Commented] (LUCENE-6776) Randomized planet model shows up additional XYZBounds errors

[ https://issues.apache.org/jira/browse/LUCENE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734998#comment-14734998 ] Michael McCandless commented on LUCENE-6776: I've been beasting this last patch for ~6 hours

Re: 5.3.1 bug fix release

I would like to port the following: From branch_5x: * SOLR-7972: Fix VelocityResponseWriter template encoding issue. Templates must be UTF-8 encoded. (Erik Hatcher) * SOLR-7929: SimplePostTool (also bin/post) -filetypes "*" now works properly in 'web' mode (Erik Hatcher) And get SOLR-7978

[jira] [Comment Edited] (SOLR-7435) NPE in FieldCollapsingQParser

[ https://issues.apache.org/jira/browse/SOLR-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735003#comment-14735003 ] Brandon Chapman edited comment on SOLR-7435 at 9/8/15 3:40 PM: ---

[jira] [Commented] (SOLR-8016) CloudSolrClient has extremely verbose error logging

[ https://issues.apache.org/jira/browse/SOLR-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734935#comment-14734935 ] Mark Miller commented on SOLR-8016: --- I think it is incorrect logging levels. This method is expected to

  1   2   >