[jira] [Resolved] (LUCENE-6906) Lucene54DocValuesFormat bug when a large segment does not have values

[ https://issues.apache.org/jira/browse/LUCENE-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand resolved LUCENE-6906. -- Resolution: Fixed Fix Version/s: 5.4 6.0 > Lucene54DocValuesFormat

[jira] [Commented] (SOLR-8330) Remove unintentionally shared loggers.

[ https://issues.apache.org/jira/browse/SOLR-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022800#comment-15022800 ] Mark Miller commented on SOLR-8330: --- bq. In that scenario, I would be in favor of removing logB, since

[jira] [Commented] (SOLR-8330) Remove unintentionally shared loggers.

[ https://issues.apache.org/jira/browse/SOLR-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022805#comment-15022805 ] Mark Miller commented on SOLR-8330: --- Anyway, beside multiple loggers per class file being annoying,

[jira] [Commented] (LUCENE-6906) Lucene54DocValuesFormat bug when a large segment does not have values

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

Re: documentation-lint failures on 5x branch?

My bad. I'll fix this afternoon. Sorry about that. > On Nov 23, 2015, at 13:35, Chris Hostetter wrote: > > > I'm seeing the failures from documentation-lint on the 5x branch when running > ant precommit (both using java7 and java8) ... see below. > > 1) is it my

[jira] [Commented] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

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

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.7.0_80) - Build # 14722 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14722/ Java: 64bit/jdk1.7.0_80 -XX:+UseCompressedOops -XX:+UseSerialGC All tests passed Build Log: [...truncated 62140 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete] Deleting

[jira] [Commented] (LUCENE-6905) GeoPointDistanceQuery using wrapped lon for dateline crossing query

[ https://issues.apache.org/jira/browse/LUCENE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022849#comment-15022849 ] Nicholas Knize commented on LUCENE-6905: bq. For the record, MBR in geo speak means "minimum

[jira] [Commented] (LUCENE-6906) Lucene54DocValuesFormat bug when a large segment does not have values

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

Re: documentation-lint failures on 5x branch?

I think the problem is that the HLL class, which is public, references the ISchemaVersion interface in its public API, which is pkg-private? So javadoc does not generate documentation for ISchemaVersion (since it is pkg-private) but still builds links to it from HLL since it is referenced in

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

This is me, I only tested lucene-core when backporting. Sorry for the noise, I'll push a fix. Le lun. 23 nov. 2015 à 20:16, a écrit : > *BUILD FAILURE* > Build URL > http://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/72824/ >

Re: [JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_66) - Build # 15013 - Failure!

I broke this. I'll fix this afternoon. Erik > On Nov 23, 2015, at 13:37, Policeman Jenkins Server > wrote: > > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15013/ > Java: 64bit/jdk1.8.0_66 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC > > All tests

[jira] [Assigned] (LUCENE-6900) Grouping sortWithinGroup should use Sort.RELEVANCE to indicate that, not null

[ https://issues.apache.org/jira/browse/LUCENE-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley reassigned LUCENE-6900: Assignee: David Smiley > Grouping sortWithinGroup should use Sort.RELEVANCE to indicate

[jira] [Updated] (LUCENE-6900) Grouping sortWithinGroup should use Sort.RELEVANCE to indicate that, not null

[ https://issues.apache.org/jira/browse/LUCENE-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-6900: - Attachment: LUCENE_6900.patch Here is a patch. There are some edits I did just for code

Benchmarking Lucene

Hi all, I work for a JVM vendor, and we're interested in obtaining / creating a set of Lucene benchmarks for internal use. We plan to use these for performance regression testing and general performance analysis (i.e. to make sure Lucene performs well on our JVM). I'm especially interested in

[jira] [Commented] (LUCENE-6905) GeoPointDistanceQuery using wrapped lon for dateline crossing query

[ https://issues.apache.org/jira/browse/LUCENE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022854#comment-15022854 ] Nicholas Knize commented on LUCENE-6905: Jenkins did catch this, eventually. Looking at the

[jira] [Updated] (LUCENE-6905) GeoPointDistanceQuery using wrapped lon for dateline crossing query

[ https://issues.apache.org/jira/browse/LUCENE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Knize updated LUCENE-6905: --- Attachment: LUCENE-6905.patch New patch to focus on unwrapping only. >

[jira] [Commented] (SOLR-8324) Logger Untanglement

[ https://issues.apache.org/jira/browse/SOLR-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022633#comment-15022633 ] Mike Drob commented on SOLR-8324: - I hadn't had a chance to start on the MethodHandles patch, feel free to

Re: Custom Facet Scoring

Hello Colleagues, I'll commit if you provide a patch, attached to the jira of course. But it should work with SolrCloud too. On Mon, Nov 23, 2015 at 9:05 PM, Ryan Josal wrote: > +1 for making new facet sorts easier to implement. I implemented an order > where the come back in

[JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.8.0_66) - Build # 5416 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5416/ Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseG1GC 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.core.TestLazyCores Error Message: ERROR: SolrIndexSearcher opens=51 closes=50 Stack Trace:

[jira] [Commented] (LUCENE-6801) PhraseQuery incorrectly advertises it supports terms at the same position

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

documentation-lint failures on 5x branch?

I'm seeing the failures from documentation-lint on the 5x branch when running ant precommit (both using java7 and java8) ... see below. 1) is it my imagination of are the smokerelease jobs on jenkins not running documentation-lint? i don't see it in the logs...

[jira] [Resolved] (LUCENE-6801) PhraseQuery incorrectly advertises it supports terms at the same position

[ https://issues.apache.org/jira/browse/LUCENE-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley resolved LUCENE-6801. -- Resolution: Fixed Assignee: David Smiley Fix Version/s: 5.4 > PhraseQuery

Re: Custom Facet Scoring

+1 for making new facet sorts easier to implement. I implemented an order where the come back in order they are first seen in the doclist, but it didn't come out very clean. My approach was to extend FacetComponent, and resort the facets by pulling them out of the results and putting them back

[jira] [Commented] (LUCENE-6906) Lucene54DocValuesFormat bug when a large segment does not have values

[ https://issues.apache.org/jira/browse/LUCENE-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022610#comment-15022610 ] Adrien Grand commented on LUCENE-6906: -- There are quite fast indeed (I did not test with SimpleText

[jira] [Commented] (LUCENE-6801) PhraseQuery incorrectly advertises it supports terms at the same position

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

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_66) - Build # 15013 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15013/ Java: 64bit/jdk1.8.0_66 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC All tests passed Build Log: [...truncated 61750 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete]

[jira] [Commented] (SOLR-8330) Remove unintentionally shared loggers.

[ https://issues.apache.org/jira/browse/SOLR-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022696#comment-15022696 ] Yonik Seeley commented on SOLR-8330: I was coming from the POV of supporting a user/customer... i.e.

[JENKINS] Lucene-Solr-5.x-Windows (64bit/jdk1.8.0_66) - Build # 5286 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/5286/ Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseParallelGC All tests passed Build Log: [...truncated 62291 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete] Deleting

Re: Benchmarking Lucene

On Mon, Nov 23, 2015 at 2:42 PM, Sanjoy Das wrote: > Hi all, > > I work for a JVM vendor, and we're interested in obtaining / creating > a set of Lucene benchmarks for internal use. We plan to use these for > performance regression testing and general performance

Re: Benchmarking Lucene

Which JVM vendor :) There are not so many, unfortunately... I run nightly benchmarks for Lucene, which are visible at https://people.apache.org/~mikemccand/lucenebench/ We use this to catch accidental performance regressions... the sources for all of this are at

[jira] [Commented] (SOLR-8329) SchemaSimilarityFactory should support a config option for the defaultSimilarity

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

Re: Benchmarking Lucene

Michael McCandless wrote: > Which JVM vendor :) There are not so many, unfortunately... I work for Azul Systems (https://www.azul.com). > I run nightly benchmarks for Lucene, which are visible at > https://people.apache.org/~mikemccand/lucenebench/ > > We use this to catch accidental

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 3794 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3794/ All tests passed Build Log: [...truncated 62266 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete] Deleting directory

Re: Benchmarking Lucene

Robert Muir wrote: > On Mon, Nov 23, 2015 at 2:42 PM, Sanjoy Das > wrote: >> Hi all, >> >> I work for a JVM vendor, and we're interested in obtaining / creating >> a set of Lucene benchmarks for internal use. We plan to use these for >> performance regression

[JENKINS] Lucene-Solr-5.x-Solaris (64bit/jdk1.8.0) - Build # 204 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/204/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.security.TestAuthorizationFramework.authorizationFrameworkTest Error Message: There are still nodes recoverying -

[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value

[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021774#comment-15021774 ] Dominik Siebel commented on SOLR-7169: -- Since this task seems to be "IN PROGRESS" already: I have a

[jira] [Commented] (SOLR-8323) Add CollectionWatcher API to ZkStateReader

[ https://issues.apache.org/jira/browse/SOLR-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021785#comment-15021785 ] Alan Woodward commented on SOLR-8323: - bq. Someone should remove stateformat=1 for Solr 6 in an ideal

[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value

[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021786#comment-15021786 ] Ishan Chattopadhyaya commented on SOLR-7169: I think it is always a good idea to have patches.

[jira] [Commented] (SOLR-8194) Improve error reporting UpdateRequest

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

[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value

[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021939#comment-15021939 ] Dominik Siebel commented on SOLR-7169: -- [~ichattopadhyaya] Thanks, it's not my first change ;) Is it

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

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/861/ 1 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestReplicateAfterCoreReload Error Message: expected:<[{indexVersion=1448273855560,generation=2,filelist=[_3zm.cfe, _3zm.cfs, _3zm.si, _3zn.fdt,

[jira] [Commented] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

[ https://issues.apache.org/jira/browse/SOLR-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021875#comment-15021875 ] Jens Wille commented on SOLR-7912: -- Both tests are passing for me on current trunk (r1715745) with the

[jira] [Updated] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

[ https://issues.apache.org/jira/browse/SOLR-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Wille updated SOLR-7912: - Attachment: SOLR-7912.patch > Add support for boost and exclude the queried document id in MoreLikeThis >

[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value

[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022065#comment-15022065 ] Dominik Siebel commented on SOLR-7169: -- Seems like it works :D > init.d status command has incorrect

[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value

[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022063#comment-15022063 ] ASF GitHub Bot commented on SOLR-7169: -- GitHub user dsiebel opened a pull request:

[jira] [Resolved] (LUCENE-6893) factor out CorePlusQueriesParser from CorePlusExtensionsParser

[ https://issues.apache.org/jira/browse/LUCENE-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke resolved LUCENE-6893. - Resolution: Fixed > factor out CorePlusQueriesParser from

[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value

[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022001#comment-15022001 ] Upayavira commented on SOLR-7169: - The Solr development community does not make much collective use of

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

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/653/ 1 tests failed. FAILED: org.apache.solr.cloud.CloudExitableDirectoryReaderTest.test Error Message: No live SolrServers available to handle this request:[http://127.0.0.1:46240/collection1] Stack Trace:

[GitHub] lucene-solr pull request: SOLR-7169: Use proper exit code in `stat...

GitHub user dsiebel opened a pull request: https://github.com/apache/lucene-solr/pull/212 SOLR-7169: Use proper exit code in `status` command to signal process status As reported in [SOLR-7169](https://issues.apache.org/jira/browse/SOLR-7169) the solr run script always return `0`

[jira] [Commented] (SOLR-8277) (Search|Top)GroupsFieldCommand tweaks

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

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

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3792/ 1 tests failed. FAILED: org.apache.solr.cloud.overseer.ZkStateWriterTest.testExternalModificationToStateFormat2 Error Message: Stack Trace: java.lang.AssertionError at

[jira] [Commented] (LUCENE-6849) Add IndexWriter API to write segment(s) without refreshing them

[ https://issues.apache.org/jira/browse/LUCENE-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021739#comment-15021739 ] Simon Willnauer commented on LUCENE-6849: - nice change - simple but powerful, seems like we got

[jira] [Resolved] (SOLR-8194) Improve error reporting UpdateRequest

[ https://issues.apache.org/jira/browse/SOLR-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward resolved SOLR-8194. - Resolution: Fixed Thanks Markus! > Improve error reporting UpdateRequest >

[jira] [Updated] (SOLR-8194) Improve error reporting UpdateRequest

[ https://issues.apache.org/jira/browse/SOLR-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward updated SOLR-8194: Attachment: SOLR-8194.patch Patch adding Objects.requireNonNull() checks to the various

[jira] [Commented] (SOLR-8194) Improve error reporting UpdateRequest

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

[jira] [Commented] (LUCENE-6801) PhraseQuery incorrectly advertises it supports terms at the same position

[ https://issues.apache.org/jira/browse/LUCENE-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022088#comment-15022088 ] David Smiley commented on LUCENE-6801: -- I'll commit this in a few hours. It'll be nice to have these

Custom Facet Scoring

Hi all, we would like to add a custom sorting for facets in addition to the existing 'index' and 'count' that can be passed by a new value for the facet.sort parameter. The aim is to achieve a prefix based sorting for all the terms of a complex field with entries of the form / /

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023246#comment-15023246 ] Shawn Heisey commented on SOLR-8333: Since ConcurrentLFUCache was my creation (mostly based on

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.8.0_66) - Build # 14723 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14723/ Java: 64bit/jdk1.8.0_66 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC All tests passed Build Log: [...truncated 62335 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete]

Re: documentation-lint failures on 5x branch?

On 23 November 2015 at 15:41, Chris Hostetter wrote: > Does anybody understand the javadoc link generation enough to > understand why it isn't always trying to create links for these package > private classes? is there a way we can force it to always > create links so

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

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/656/ All tests passed Build Log: [...truncated 61608 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete] Deleting directory

[JENKINS] Lucene-Solr-5.x-MacOSX (64bit/jdk1.8.0) - Build # 2834 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/2834/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC All tests passed Build Log: [...truncated 62241 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete]

[jira] [Updated] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey updated SOLR-8333: --- Attachment: SOLR-8333-ConcurrentLFUCache-protected.patch Possible patch for ConcurrentLFUCache -- this

[jira] [Created] (SOLR-8335) HdfsLockFactory does not allow core to come up after a node was killed

Varun Thacker created SOLR-8335: --- Summary: HdfsLockFactory does not allow core to come up after a node was killed Key: SOLR-8335 URL: https://issues.apache.org/jira/browse/SOLR-8335 Project: Solr

[jira] [Updated] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

[ https://issues.apache.org/jira/browse/SOLR-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-7912: --- Attachment: SOLR-7912-test-fix.patch Beasting this patch. Will commit if it works fine. > Add support

[jira] [Reopened] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

[ https://issues.apache.org/jira/browse/SOLR-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reopened SOLR-7912: Reopening to fix failing test > Add support for boost and exclude the queried document id in

[jira] [Commented] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

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

[jira] [Commented] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

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

[jira] [Commented] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

[ https://issues.apache.org/jira/browse/SOLR-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023791#comment-15023791 ] Anshum Gupta commented on SOLR-7912: It makes sense to not assert against the parsed queries when there

[jira] [Commented] (SOLR-7912) Add support for boost and exclude the queried document id in MoreLikeThis QParser

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

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 3796 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3796/ 1 tests failed. FAILED: org.apache.solr.search.mlt.CloudMLTQParserTest.test Error Message: array lengths differed, expected.length=2 actual.length=1 Stack Trace: java.lang.AssertionError: array lengths differed,

[JENKINS] Lucene-Solr-5.x-Linux (32bit/jdk1.7.0_80) - Build # 14726 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/14726/ Java: 32bit/jdk1.7.0_80 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.search.mlt.CloudMLTQParserTest.test Error Message: array lengths differed, expected.length=2 actual.length=1 Stack Trace:

[jira] [Updated] (SOLR-8299) ConfigSet DELETE should not allow deletion of a a configset that's currently being used

[ https://issues.apache.org/jira/browse/SOLR-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8299: --- Attachment: SOLR-8299.patch Updated patch with a test. If a collection is in use, the call would now

[jira] [Commented] (SOLR-8326) Adding read restriction to BasicAuth + RuleBased authorization causes issue with replication

[ https://issues.apache.org/jira/browse/SOLR-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023479#comment-15023479 ] Anshum Gupta commented on SOLR-8326: Seems like this isn't the root of the problem. As reported on the

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023477#comment-15023477 ] Erik Hatcher commented on SOLR-8333: I went ahead and committed the fix to SPT and its test to knock

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023493#comment-15023493 ] Erik Hatcher commented on SOLR-8333: While these issues the documentation checker found are mostly

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023508#comment-15023508 ] Hoss Man commented on SOLR-8333: erik: please do not conflate/convolute 2 independent issues. Regardless

[jira] [Commented] (SOLR-8307) XXE Vulnerability

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

Re: Custom Facet Scoring

I don't have the time to work on this issue right now, but I can definitely help test it and port my facet sort to it if somebody works on it to see how it works. On Monday, November 23, 2015, Mikhail Khludnev wrote: > Hello Colleagues, > > I'll commit if you provide

[jira] [Reopened] (SOLR-8307) XXE Vulnerability

[ https://issues.apache.org/jira/browse/SOLR-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man reopened SOLR-8307: the commits made for this issue have broken trunk and 5x builds due to causing the javadocs to produce broken

[jira] [Commented] (SOLR-8307) XXE Vulnerability

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

[jira] [Commented] (SOLR-8307) XXE Vulnerability

[ https://issues.apache.org/jira/browse/SOLR-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023554#comment-15023554 ] Erik Hatcher commented on SOLR-8307: [~hossman_luc...@fucit.org] - should be fixed now. I moved

[jira] [Assigned] (SOLR-8326) Adding read restriction to BasicAuth + RuleBased authorization causes issue with replication

[ https://issues.apache.org/jira/browse/SOLR-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul reassigned SOLR-8326: Assignee: Noble Paul > Adding read restriction to BasicAuth + RuleBased authorization causes issue

[jira] [Updated] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Hatcher updated SOLR-8333: --- Attachment: SOLR-8333.patch And here's a patch for several items that popped up in my `ant precommit`.

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 3795 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3795/ All tests passed Build Log: [...truncated 62311 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete] Deleting directory

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

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

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

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

[JENKINS] Lucene-Solr-trunk-Solaris (64bit/jdk1.8.0) - Build # 208 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/208/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseG1GC All tests passed Build Log: [...truncated 61673 lines...] -documentation-lint: [jtidy] Checking for broken html (such as invalid tags)... [delete] Deleting

[jira] [Commented] (SOLR-8326) Adding read restriction to BasicAuth + RuleBased authorization causes issue with replication

[ https://issues.apache.org/jira/browse/SOLR-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023502#comment-15023502 ] Anshum Gupta commented on SOLR-8326: Seems like the timestamp in the header received on the node that

[jira] [Commented] (SOLR-8333) fix public methods that take/return private/package-private arguments/results

[ https://issues.apache.org/jira/browse/SOLR-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023520#comment-15023520 ] Erik Hatcher commented on SOLR-8333: I've confirmed that "ant documentation-lint" is happy when:

[JENKINS] Lucene-Solr-5.x-Solaris (multiarch/jdk1.7.0) - Build # 206 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/206/ Java: multiarch/jdk1.7.0 -d32 -server -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.search.mlt.CloudMLTQParserTest.test Error Message: array lengths differed, expected.length=2 actual.length=1 Stack Trace:

[jira] [Updated] (SOLR-8334) Highlighting content field problem when using JiebaTokenizerFactory

[ https://issues.apache.org/jira/browse/SOLR-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeo Zheng Lin updated SOLR-8334: Description: When I tried to use the JiebaTokenizerFactory to index Chinese characters in Solr, it

[JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 390 - Failure

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

[jira] [Created] (SOLR-8334) Highlighting content field problem when using JiebaTokenizerFactory

Yeo Zheng Lin created SOLR-8334: --- Summary: Highlighting content field problem when using JiebaTokenizerFactory Key: SOLR-8334 URL: https://issues.apache.org/jira/browse/SOLR-8334 Project: Solr

[jira] [Updated] (SOLR-8334) Highlighting content field problem when using JiebaTokenizerFactory

[ https://issues.apache.org/jira/browse/SOLR-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeo Zheng Lin updated SOLR-8334: Attachment: JiebaSegmenter.java This is the modified JiebaSegmenter.java which allows the

[jira] [Updated] (SOLR-8334) Highlighting content field problem when using JiebaTokenizerFactory

[ https://issues.apache.org/jira/browse/SOLR-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeo Zheng Lin updated SOLR-8334: Environment: Windows 8.1, Solr 5.3, ZooKeeper 3.4.6, jieba-analysis-1.0.0 (was: Windows 8.1, Solr

[JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.8.0_66) - Build # 5417 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5417/ Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.handler.PingRequestHandlerTest.testPingInClusterWithNoHealthCheck Error Message: Could not find a healthy node to

[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk1.9.0-ea-b90) - Build # 15018 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15018/ Java: 32bit/jdk1.9.0-ea-b90 -server -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: Error from server at http://127.0.0.1:56737/rusuj/awholynewcollection_0:

Re: Custom Facet Scoring

Thanks a lot for your feedback - I will try to pursue the approach indicated and see how far we can get. On 24.11.2015 01:46, Ryan Josal wrote: I don't have the time to work on this issue right now, but I can definitely help test it and port my facet sort to it if somebody works on it to see

  1   2   >