[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

[jira] [Commented] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

[ https://issues.apache.org/jira/browse/SOLR-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112530#comment-15112530 ] Shalin Shekhar Mangar commented on SOLR-8582: - Thanks Noble. Your patch fixes the slowdown:

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

> On Jan 22, 2016, at 2:28 PM, Dawid Weiss wrote: > > 1) I'd notify infra because this permits any committer to destroy the > log history without a trace ;) For Lucene anyway (and I suspect most/all ASF projects?), there is an (out-of-band) trace: the archive of log

[jira] [Commented] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113100#comment-15113100 ] Keith Laban commented on SOLR-8559: --- After a doing some performance testing, this change shows about 4

Re: [JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15617 - Still Failing!

Patch for these nagging failures is under review. Commit coming soon. On Fri, Jan 22, 2016 at 1:55 PM, Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15617/ > Java: 32bit/jdk-9-ea+95 -server -XX:+UseSerialGC

[jira] [Commented] (LUCENE-6978) Make LuceneTestCase use language tags instead of parsing locales by hand

[ https://issues.apache.org/jira/browse/LUCENE-6978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113036#comment-15113036 ] Uwe Schindler commented on LUCENE-6978: --- I know why this happens. Will fix later. It is only partly

[jira] [Commented] (LUCENE-6978) Make LuceneTestCase use language tags instead of parsing locales by hand

[ https://issues.apache.org/jira/browse/LUCENE-6978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113020#comment-15113020 ] Steve Rowe commented on LUCENE-6978: My Jenkins found a reproducible locale-triggered DIH failure on

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

On Jan 22, 2016, at 2:41 PM, Dawid Weiss wrote: > >> Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties >> (of which svn:log is one) cause the property's previous value to be >> permanently discarded” > > Hmm... They're not versioned in the SVN

[jira] [Commented] (LUCENE-6974) TesGeoPointQuery failures: some hits were wrong (should not match but did)

[ https://issues.apache.org/jira/browse/LUCENE-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112989#comment-15112989 ] Nicholas Knize commented on LUCENE-6974: It can be resolved. Looks like I don't have that power

[jira] [Updated] (SOLR-8573) Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings

[ https://issues.apache.org/jira/browse/SOLR-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8573: --- Summary: Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings (was:

[jira] [Updated] (SOLR-8573) Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings

[ https://issues.apache.org/jira/browse/SOLR-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8573: --- Attachment: SOLR-8573.patch Implemented clearWarnings/getWarnings for Connection, Statement, and

[jira] [Commented] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113133#comment-15113133 ] David Smiley commented on SOLR-8559: [~dpgove] Please update the "Fix Version/s:" when resolving issues

[jira] [Reopened] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Gove reopened SOLR-8559: --- > FCS facet performance optimization > -- > > Key:

[jira] [Updated] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Gove updated SOLR-8559: -- Fix Version/s: (was: Trunk) 5.5 > FCS facet performance optimization >

[jira] [Updated] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Gove updated SOLR-8559: -- Affects Version/s: (was: 5.4) 5.5 > FCS facet performance optimization >

[jira] [Resolved] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Gove resolved SOLR-8559. --- Resolution: Implemented > FCS facet performance optimization > -- > >

[jira] [Commented] (SOLR-8559) FCS facet performance optimization

[ https://issues.apache.org/jira/browse/SOLR-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113160#comment-15113160 ] Dennis Gove commented on SOLR-8559: --- Thanks, Dave. I think I've been marking issues as closed. I'll keep

[jira] [Resolved] (LUCENE-6974) TesGeoPointQuery failures: some hits were wrong (should not match but did)

[ https://issues.apache.org/jira/browse/LUCENE-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Knize resolved LUCENE-6974. Resolution: Resolved > TesGeoPointQuery failures: some hits were wrong (should not match

Re: [JENKINS-EA] Lucene-Solr-5.x-Linux (32bit/jdk-9-ea+95) - Build # 15321 - Failure!

I fixed this already... Mike McCandless http://blog.mikemccandless.com On Fri, Jan 22, 2016 at 2:17 PM, Policeman Jenkins Server wrote: > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15321/ > Java: 32bit/jdk-9-ea+95 -client -XX:+UseParallelGC

[jira] [Commented] (LUCENE-6978) Make LuceneTestCase use language tags instead of parsing locales by hand

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

[jira] [Commented] (LUCENE-6978) Make LuceneTestCase use language tags instead of parsing locales by hand

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

[jira] [Commented] (LUCENE-6978) Make LuceneTestCase use language tags instead of parsing locales by hand

[ https://issues.apache.org/jira/browse/LUCENE-6978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113110#comment-15113110 ] Uwe Schindler commented on LUCENE-6978: --- Issue should be fixed now. The problem is the

[jira] [Commented] (SOLR-8502) Improve Solr JDBC Driver to support SQL Clients like DBVisualizer

[ https://issues.apache.org/jira/browse/SOLR-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113111#comment-15113111 ] Joel Bernstein commented on SOLR-8502: -- Looks like you've got a number of tickets ready to go. Can you

[jira] [Commented] (SOLR-8550) Add asynchronous DaemonStreams to the Streaming API

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

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Does anyone here know how to edit a log message after committing? I accidentally typed in lucene instead of solr for one of the release related commits. On Fri, Jan 22, 2016 at 11:03 AM, Anshum Gupta wrote: > Hi Adrien, > > I'm in the middle of publishing the artifacts.

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

I'm sorry, I wasn't precise enough -- have you tried it on the Apache SVN? Quote: "The first way is for the repository administrator to enable revision property modifications." I admit I didn't check, but I'd be surprised if these were allowed as this permits historical changes to the content of

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Adrien, Seems like I'd have to wait until the release is on a decent number of Apache mirrors. Running addBackcompatIndexes.py for 5.3.2 leads to the following error: Could not find version 5.3.2 in apache mirror or archives Is there a work around for this? On Fri, Jan 22, 2016 at 7:58 AM,

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

> Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties > (of which svn:log is one) cause the property's previous value to be > permanently discarded” Hmm... They're not versioned in the SVN dumps I looked at? In any case, I wouldn't do it, Anshum -- if it's a typo, it's

[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15617 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15617/ Java: 32bit/jdk-9-ea+95 -server -XX:+UseSerialGC -XX:-CompactStrings 1 tests failed. FAILED: org.apache.lucene.search.TestLatLonPointQueries.testMultiValued Error Message: some hits were wrong Stack Trace:

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Thanks Steve, but seems like that required 'admin' permissions. Not sure if I/we have it. Dawid: Thanks. I've used stuff from that point on so I don't think I'll be able to revert it. In any case, The commit message is about copying rc to the release repo and has 'lucene' instead of 'solr'. I

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Again, not true :) In modern versions of Subversion, properties are also versioned. So, no history destruction to see here. -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:28 PM, Dawid Weiss wrote: > > Interesting! If it does work then: > > 1) I'd notify infra

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties (of which svn:log is one) cause the property's previous value to be permanently discarded” Digging… -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:30 PM, Steve Rowe wrote: > > Again, not true

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

[JENKINS-EA] Lucene-Solr-5.x-Linux (32bit/jdk-9-ea+95) - Build # 15321 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15321/ Java: 32bit/jdk-9-ea+95 -client -XX:+UseParallelGC -XX:-CompactStrings 1 tests failed. FAILED: org.apache.lucene.store.TestRAFDirectory.testSeekBeyondEndOfFile Error Message: didn't hit expected exception Stack Trace:

[jira] [Updated] (SOLR-8587) Add segments file information to core admin status

[ https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated SOLR-8587: - Attachment: SOLR-8587.patch Simple patch. I didn't find tests that cover this stuff, not directly at

[jira] [Updated] (SOLR-8519) Implement ResultSetMetaDataImpl.getColumnCount()

[ https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8519: --- Flags: Patch > Implement ResultSetMetaDataImpl.getColumnCount() >

[jira] [Commented] (SOLR-8466) Add support for UnInvertedField based faceting to FacetComponent

[ https://issues.apache.org/jira/browse/SOLR-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112930#comment-15112930 ] Mikhail Khludnev commented on SOLR-8466: Reviewing patch: SimpleFacets changes make sense, there is

[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15616 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15616/ Java: 32bit/jdk-9-ea+95 -server -XX:+UseConcMarkSweepGC -XX:-CompactStrings 1 tests failed. FAILED: org.apache.lucene.search.TestLatLonPointQueries.testAllLonEqual Error Message: Captured an uncaught exception in thread:

[jira] [Updated] (SOLR-8519) Implement ResultSetMetaDataImpl.getColumnCount()

[ https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8519: --- Attachment: SOLR-8519.patch This patch adds some framework to get information about a tuples fields

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

No way to do it in SVN. You can revert your commit and commit the same one again, with proper message. In the git world this would be possible (locally, with git commit --amend), but after you push to a remote repository this would be discouraged and the same way as above would be advised since

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Not true - you can fix it in SVN. From : svn propset -r N --revprop svn:log "new log message” URL -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:13 PM, Dawid Weiss wrote: > > No way to do it in SVN. You can

[jira] [Created] (SOLR-8587) Add segments file information to core admin status

Shai Erera created SOLR-8587: Summary: Add segments file information to core admin status Key: SOLR-8587 URL: https://issues.apache.org/jira/browse/SOLR-8587 Project: Solr Issue Type:

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Interesting! If it does work then: 1) I'd notify infra because this permits any committer to destroy the log history without a trace ;) 2) the consequences for git mirrors of any project that did such a change are also interesting -- incremental git svn won't pick these up and effectively the

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

[JENKINS-EA] Lucene-Solr-5.4-Linux (32bit/jdk-9-ea+95) - Build # 440 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.4-Linux/440/ Java: 32bit/jdk-9-ea+95 -server -XX:+UseParallelGC -XX:-CompactStrings 3 tests failed. FAILED: org.apache.solr.handler.dataimport.TestTikaEntityProcessor.testEmbeddedDocsLegacy Error Message: Stack Trace:

[JENKINS] Lucene-Solr-NightlyTests-5.3 - Build # 17 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.3/17/ 1 tests failed. FAILED: org.apache.solr.cloud.hdfs.StressHdfsTest.test Error Message: No registered leader was found after waiting for 3ms , collection: delete_data_dir slice: shard4 Stack Trace:

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Hi, Works on Apache Lucene without problems. Not sure about distribution repo. Used it several times to fix typos in issue number. Only JIRA robot does not get it, so it won't auto-comment. Uwe Am 22. Januar 2016 20:21:29 MEZ, schrieb Dawid Weiss : >I'm sorry, I wasn't

[jira] [Updated] (SOLR-8517) Implement minimal set of get* methods in ResultSetImpl for column names

[ https://issues.apache.org/jira/browse/SOLR-8517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8517: --- Flags: Patch > Implement minimal set of get* methods in ResultSetImpl for column names >

[jira] [Updated] (SOLR-8517) Implement minimal set of get* methods in ResultSetImpl for column names

[ https://issues.apache.org/jira/browse/SOLR-8517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8517: --- Attachment: SOLR-8517.patch This patch adds some get* methods for column names and adds checks for

[jira] [Commented] (LUCENE-6932) Seek past EOF with RAMDirectory should throw EOFException

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

[jira] [Commented] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

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

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

I'll fix! Mike McCandless On Fri, Jan 22, 2016 at 1:55 PM, wrote: > *BUILD FAILURE* > > Build URL > http://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/79964/ > Project: lucene_linux_java8_64_test_only > Randomization: JDKEA8,local,heap[1024m],-server +UseG1GC >

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Hi Adrien, I'm in the middle of publishing the artifacts. I should be able to get to it in just a bit. Thanks for reminding. On Fri, Jan 22, 2016 at 7:58 AM, Adrien Grand wrote: > Anshum, I would like to draw your attention to the fact that Dawid plans > to start the git

[jira] [Updated] (SOLR-8519) Implement ResultSetMetaDataImpl.getColumnCount()

[ https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8519: --- Attachment: SOLR-8519.patch Improve patch to not create ResultSetMetaData on each call to

[jira] [Commented] (SOLR-8502) Improve Solr JDBC Driver to support SQL Clients like DBVisualizer

[ https://issues.apache.org/jira/browse/SOLR-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112916#comment-15112916 ] Kevin Risden commented on SOLR-8502: [~joel.bernstein] - Can you take a look at SOLR-8573 and

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Seems to have worked for Dennis: http://lucene.472066.n3.nabble.com/Update-commit-message-td4249465.html#a4249469 On Sat, Jan 23, 2016 at 12:51 AM, Dawid Weiss wrote: > I'm sorry, I wasn't precise enough -- have you tried it on the Apache > SVN? Quote: > > "The first way

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

I'll leave it as is. I don't think this is a cause of concern. Thanks to you and Steve for all the suggestions! On Fri, Jan 22, 2016 at 11:41 AM, Dawid Weiss wrote: > > Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision > properties (of which svn:log is

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

I've added the back-compat indexes for 5.3.2 to lucene_solr_5_3, branch_5x, and trunk. Think we are good to go in terms the 5.3.2 release-svn dependency. On Fri, Jan 22, 2016 at 11:41 AM, Anshum Gupta wrote: > Adrien, > > Seems like I'd have to wait until the release is

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Thanks. Fixed a trivial typo in the Solr notes: "Solr 5.3.1 includes 11 bug fixes” —> "Solr 5.3.2 includes 11 bug fixes" -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 21. jan. 2016 kl. 20.16 skrev Anshum Gupta : > > The vote has

[jira] [Assigned] (SOLR-8466) Add support for UnInvertedField based faceting to FacetComponent

[ https://issues.apache.org/jira/browse/SOLR-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev reassigned SOLR-8466: -- Assignee: Mikhail Khludnev > Add support for UnInvertedField based faceting to

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

I'll fix, new DFI sim still wreaking havoc! Mike McCandless On Fri, Jan 22, 2016 at 3:07 PM, wrote: > *BUILD FAILURE* > > Build URL > http://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/79972/ > Project: lucene_linux_java8_64_test_only > Randomization:

[jira] [Commented] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113266#comment-15113266 ] Hoss Man commented on SOLR-5730: bq. Any views on this alternative? +1 > make Lucene's SortingMergePolicy

[jira] [Commented] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113257#comment-15113257 ] Christine Poerschke commented on SOLR-5730: --- *Any thoughts on how crucial support for the enable

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

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/916/ 2 tests failed. FAILED: org.apache.lucene.search.TestGeoPointQuery.testRandomBig Error Message: CheckIndex failed Stack Trace: java.lang.RuntimeException: CheckIndex failed at

[jira] [Created] (SOLR-8581) Integration tests for rolling upgrades

Vivek Narang created SOLR-8581: -- Summary: Integration tests for rolling upgrades Key: SOLR-8581 URL: https://issues.apache.org/jira/browse/SOLR-8581 Project: Solr Issue Type: Test

[JENKINS-EA] Lucene-Solr-5.x-Linux (32bit/jdk-9-ea+95) - Build # 15317 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15317/ Java: 32bit/jdk-9-ea+95 -server -XX:+UseSerialGC -XX:-CompactStrings 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.SaslZkACLProviderTest Error Message: 5 threads leaked from SUITE scope at

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15614/ Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.CollectionsAPIDistributedZkTest Error Message: 5 threads leaked from SUITE scope at

[jira] [Updated] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

[ https://issues.apache.org/jira/browse/SOLR-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-8582: - Attachment: SOLR-8582.patch > /update/json/docs is 4x slower than /update for indexing a list of json docs

Re: Question about release plans amidst the git transition

Thanks Uwe, much appreciated. Dawid On Fri, Jan 22, 2016 at 1:55 PM, Uwe Schindler wrote: > I am on a trip in Amsterdam, returning this evening. I will take care of > Jenkins! Will update Policeman's JDKs, too, and install all necessary Git > tools on Slave VMs. > > Uwe > > Am

[jira] [Created] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

Shalin Shekhar Mangar created SOLR-8582: --- Summary: /update/json/docs is 4x slower than /update for indexing a list of json docs Key: SOLR-8582 URL: https://issues.apache.org/jira/browse/SOLR-8582

Re: Question about release plans amidst the git transition

So, we do the switch, right? Seeing the discussions and conflicting arguments/ preferences I'm no longer that enthusiastic about the whole ordeal... it feels like we're trying to disturb people in their work. Sigh. Anyway, if this experiment doesn't work we *can* revert. It's not the end of the

Re: Question about release plans amidst the git transition

I am on a trip in Amsterdam, returning this evening. I will take care of Jenkins! Will update Policeman's JDKs, too, and install all necessary Git tools on Slave VMs. Uwe Am 22. Januar 2016 13:21:40 MEZ, schrieb Dawid Weiss : >So, we do the switch, right? Seeing the

Re: [VOTE] Release Lucene/Solr 5.4.1 RC2

I modified the Solr release notes to mention the faceting bug as well, since it was bad enough to cause us to respin. Le ven. 22 janv. 2016 à 04:40, Shawn Heisey a écrit : > On 1/21/2016 8:14 PM, Michael Froh wrote: > > Should the Solr release notes reference the additional

[jira] [Updated] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

[ https://issues.apache.org/jira/browse/SOLR-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-8582: - Attachment: SOLR-8582.patch > /update/json/docs is 4x slower than /update for indexing a list of json docs

[jira] [Created] (SOLR-8583) Apply highlighting to hl.alternateField

Jan Høydahl created SOLR-8583: - Summary: Apply highlighting to hl.alternateField Key: SOLR-8583 URL: https://issues.apache.org/jira/browse/SOLR-8583 Project: Solr Issue Type: Improvement

Re: [VOTE] Release Lucene/Solr 5.4.1 RC2

Thanks Adrien for doing the release! On Fri, Jan 22, 2016 at 4:50 PM, Adrien Grand wrote: > I modified the Solr release notes to mention the faceting bug as well, > since it was bad enough to cause us to respin. > > Le ven. 22 janv. 2016 à 04:40, Shawn Heisey

Re: Question about release plans amidst the git transition

It's nothing personal, Erik! I honestly wouldn't want people to put additional effort just for the sake of saying "we've switched to git". But at the same time what's driving me is what I mentioned at the beginning -- I was reluctant to switch to git (with my other projects) at first too, but I

Re: Apache Lucene/Solr GIT migration, requesting infra help

On 01/23/2016 03:02 AM, Dawid Weiss wrote: > Hello Daniel, > > I've prepared everything for the migration and I hand it off to you (I > will be available in the morning, if you need assistance). I can also > log on to hipchat, but send me an e-mail if you wish me to. > > Here are the steps we

[jira] [Updated] (SOLR-8415) Provide command to switch between non/secure mode in ZK

[ https://issues.apache.org/jira/browse/SOLR-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated SOLR-8415: Attachment: SOLR-8415.branch_5x.patch Attaching a {{--no-prefix}} patch for branch 5. > Provide command to

[jira] [Commented] (LUCENE-6974) TesGeoPointQuery failures: some hits were wrong (should not match but did)

[ https://issues.apache.org/jira/browse/LUCENE-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112584#comment-15112584 ] Michael McCandless commented on LUCENE-6974: [~nknize], can this be closed now? >

[jira] [Commented] (LUCENE-6930) Decouple GeoPointField from NumericType

[ https://issues.apache.org/jira/browse/LUCENE-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112630#comment-15112630 ] Nicholas Knize commented on LUCENE-6930: That's unrelated to this patch. Its from nuking the

[jira] [Created] (SOLR-8586) Implement hash over all documents to check for shard synchronization

Yonik Seeley created SOLR-8586: -- Summary: Implement hash over all documents to check for shard synchronization Key: SOLR-8586 URL: https://issues.apache.org/jira/browse/SOLR-8586 Project: Solr

[jira] [Commented] (SOLR-7704) delete by query throws document id missing mandatory uniqueKey field: Id when called by JSON but works fine via XML

[ https://issues.apache.org/jira/browse/SOLR-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112699#comment-15112699 ] victorsosa commented on SOLR-7704: -- do you have any Log file??? > delete by query throws document id

[jira] [Commented] (SOLR-8586) Implement hash over all documents to check for shard synchronization

[ https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112702#comment-15112702 ] Ishan Chattopadhyaya commented on SOLR-8586: A bloom filter with all versions, maybe? >

[jira] [Commented] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

[ https://issues.apache.org/jira/browse/SOLR-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112710#comment-15112710 ] Noble Paul commented on SOLR-8582: -- Thanks > /update/json/docs is 4x slower than /update for indexing a

[jira] [Commented] (SOLR-8586) Implement hash over all documents to check for shard synchronization

[ https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112725#comment-15112725 ] Yonik Seeley commented on SOLR-8586: A bloom filter would allow one to estimate (with a known error) if

[jira] [Updated] (SOLR-8584) Phrase Fields ranking bug for range search when using edismax queryparser

[ https://issues.apache.org/jira/browse/SOLR-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Egense updated SOLR-8584: Description: When you have PhraseFields defined in your edismax parser and make a range query, the

[jira] [Updated] (SOLR-8584) Phrase Fields ranking bug for range search when using edismax queryparser

[ https://issues.apache.org/jira/browse/SOLR-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Egense updated SOLR-8584: Description: When you have PhraseFields defined in your edismax parser and make a range query, the

[jira] [Updated] (SOLR-8584) Phrase Fields ranking bug for range search when using edismax queryparser

[ https://issues.apache.org/jira/browse/SOLR-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Egense updated SOLR-8584: Description: When you have PhraseFields defined in your edismax parser and make a range query, the

[jira] [Commented] (LUCENE-6956) TestBKDTree.testRandomMedium() failure: some hits were wrong

[ https://issues.apache.org/jira/browse/LUCENE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112455#comment-15112455 ] Michael McCandless commented on LUCENE-6956: Currently we use {{1e-7}} ({{POLY_TOLERANCE}})

[jira] [Commented] (LUCENE-6986) Add more DFI independence measures

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

[JENKINS-EA] Lucene-Solr-5.4-Linux (64bit/jdk-9-ea+95) - Build # 438 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.4-Linux/438/ Java: 64bit/jdk-9-ea+95 -XX:+UseCompressedOops -XX:+UseG1GC -XX:-CompactStrings 3 tests failed. FAILED: org.apache.solr.handler.dataimport.TestTikaEntityProcessor.testEmbeddedDocsLegacy Error Message: Stack Trace:

[jira] [Created] (SOLR-8584) Phrase Fields ranking bug for range search when using edismax queryparser

Thomas Egense created SOLR-8584: --- Summary: Phrase Fields ranking bug for range search when using edismax queryparser Key: SOLR-8584 URL: https://issues.apache.org/jira/browse/SOLR-8584 Project: Solr

[jira] [Updated] (SOLR-8584) Phrase Fields ranking bug for range search when using edismax queryparser

[ https://issues.apache.org/jira/browse/SOLR-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Egense updated SOLR-8584: Description: When you have PhraseFields defined in your edismax parser and make a range query, the

[jira] [Updated] (SOLR-8584) Phrase Fields ranking bug for range search when using edismax queryparser

[ https://issues.apache.org/jira/browse/SOLR-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Egense updated SOLR-8584: Description: When you have PhraseFields defined in your edismax parser and make a range query, the

[jira] [Commented] (LUCENE-6986) Add more DFI independence measures

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

  1   2   >