[jira] [Commented] (SOLR-3731) Disallow null CoreContainer in ZkController constructor

[ https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442305#comment-13442305 ] Sami Siren commented on SOLR-3731: -- bq. I'm getting frequent fails now in OverseerTest Li

Customizing Text Search in Solr

Can anyone tell how to disable fuzzy search for text fields in solr? I have a field "name_text_en" in solr. When I search for "2930" , I get all documents with "2930" in name and also "3930" in name. Reason: Query at backend was found as: Query: q=name_text_en:( 2930^100.0 OR 2930*^50.0 OR 2930~

[jira] [Created] (LUCENE-4330) Add NAIST-jdic support to Kuromoji

Christian Moen created LUCENE-4330: -- Summary: Add NAIST-jdic support to Kuromoji Key: LUCENE-4330 URL: https://issues.apache.org/jira/browse/LUCENE-4330 Project: Lucene - Core Issue Type: Im

[jira] [Created] (SOLR-3761) Cannot flush solr (delete all existing documents)

ESSOUSSI Jamel created SOLR-3761: Summary: Cannot flush solr (delete all existing documents) Key: SOLR-3761 URL: https://issues.apache.org/jira/browse/SOLR-3761 Project: Solr Issue Type: Bug

[jira] [Commented] (LUCENE-4330) Add NAIST-jdic support to Kuromoji

[ https://issues.apache.org/jira/browse/LUCENE-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442362#comment-13442362 ] Robert Muir commented on LUCENE-4330: - this is already supported: you can enable this

[jira] [Commented] (LUCENE-4330) Add NAIST-jdic support to Kuromoji

[ https://issues.apache.org/jira/browse/LUCENE-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442363#comment-13442363 ] Robert Muir commented on LUCENE-4330: - http://code.google.com/p/mozc/issues/detail?id

[jira] [Commented] (SOLR-3761) Cannot flush solr (delete all existing documents)

[ https://issues.apache.org/jira/browse/SOLR-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442367#comment-13442367 ] Jack Krupansky commented on SOLR-3761: -- Is there any chance that you inadvertently del

[jira] [Comment Edited] (SOLR-3761) Cannot flush solr (delete all existing documents)

[ https://issues.apache.org/jira/browse/SOLR-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442367#comment-13442367 ] Jack Krupansky edited comment on SOLR-3761 at 8/27/12 11:03 PM: -

Re: Customizing Text Search in Solr

First, this kind of question is best asked on the user's list, this list is for developer-level discussion. See: http://lucene.apache.org/solr/discussion.html But on to your question: There's nothing in Solr that automatically does this, so I suspect that it's coming from hybris, I'd ask this of t

Re: Customizing Text Search in Solr

This sounds like an issue with your hybris software, not Solr. Yes, Solr supports fuzzy queries. If you don’t want a fuzzy query, then don’t send it to Solr. -- Jack Krupansky From: Pooja Goel(EMP00) Sent: Monday, August 27, 2012 6:04 AM To: dev@lucene.apache.org Subject: Customizing Text Sea

[jira] [Updated] (LUCENE-3923) fail the build on wrong svn:eol-style

[ https://issues.apache.org/jira/browse/LUCENE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-3923: Attachment: LUCENE-3923.patch here's a prototype > fail the build on wrong svn:eo

[jira] [Commented] (LUCENE-3923) fail the build on wrong svn:eol-style

[ https://issues.apache.org/jira/browse/LUCENE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442422#comment-13442422 ] Robert Muir commented on LUCENE-3923: - Yeah maybe svnkit is ok, however its license l

[jira] [Closed] (LUCENE-4224) Simplify MultiValuedCase in TermsIncludingScoreQuery

[ https://issues.apache.org/jira/browse/LUCENE-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen closed LUCENE-4224. - Resolution: Fixed Committed to trunk and branch_4x > Simplify M

Build failed in Jenkins: Lucene-trunk-Linux-Java7-64-test-only #3659

See -- [...truncated 967 lines...] [junit4:junit4] Suite: org.apache.lucene.search.TestQueryWrapperFilter [junit4:junit4] Completed on J5 in 0.87s, 3 tests [junit4:junit4] [junit4:junit4] Suite: org.apache.lucene.search.TestMultiTermConstantScore [junit4:j

Jenkins build is back to normal : Lucene-trunk-Linux-Java7-64-test-only #3660

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Resolved] (LUCENE-3923) fail the build on wrong svn:eol-style

[ https://issues.apache.org/jira/browse/LUCENE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-3923. - Resolution: Fixed Fix Version/s: 4.0 5.0 Thanks for the comments. I fi

Re: Build failed in Jenkins: Lucene-trunk-Linux-Java7-64-test-only #3659

I think this is a test bug ... I committed a fix (rev 1377711). Mike McCandless http://blog.mikemccandless.com On Mon, Aug 27, 2012 at 10:48 AM, wrote: > See > > -- > [...truncated 967 lines...] > [junit4:junit4] Suite: org.apache.lucene.search.TestQuer

[JENKINS] Lucene-Solr-Tests-4.x-java7 - Build # 358 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-java7/358/ All tests passed Build Log: [...truncated 7821 lines...] [junit4:junit4] ERROR: JVM J0 ended with an exception, command line: /usr/local/openjdk7/jre/bin/java -XX:+UseG1GC -Dtests.prefix=tests -Dtests.seed=FB73148C1A0BEDEB -X

Minor bug/annoyance: Extra parentheses for DisjunctionMaxQuery in Solr parsedquery

The output for the Solr “parsedquery” response element for DisjunctionMaxQuery has an extra set of parentheses which are at a minimum annoying, but also misleading since technically they should indicate a nested BooleanQuery, which is not the case. For example: (+DisjunctionMaxQuery((id:t

[jira] [Commented] (SOLR-139) Support updateable/modifiable documents

[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442472#comment-13442472 ] Christopher Ball commented on SOLR-139: --- Yonik, Do you have an example with the XML s

[jira] [Commented] (SOLR-2272) Join

[ https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442481#comment-13442481 ] Christopher Ball commented on SOLR-2272: This does not appear to support use with a

[jira] [Created] (SOLR-3762) NullPointerException when using grouping

Jesse MacVicar created SOLR-3762: Summary: NullPointerException when using grouping Key: SOLR-3762 URL: https://issues.apache.org/jira/browse/SOLR-3762 Project: Solr Issue Type: Bug Affec

[jira] [Commented] (SOLR-3762) NullPointerException when using grouping

[ https://issues.apache.org/jira/browse/SOLR-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442518#comment-13442518 ] Jesse MacVicar commented on SOLR-3762: -- SEVERE: null:java.lang.NullPointerException

RE: svn commit: r1377738 - /lucene/dev/trunk/build.xml

For now I added the SVN task only to the Ubuntu Linux builds on SDDS server. ASF Jenkins does not run it (because the hack uses svnkit to check repo status which spawn a JVM on every svn call) and windows does not run it, too (as fork is horribly slow on windows) Currently I am working on a sol

RE: RecursivePrefixTreeFieldType class not found

According to the document I was reading here: http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4 First, you must register a spatial field type in the Solr schema.xml file. The instructions in this whole document imply the RecursivePrefixTreeStrategy

[jira] [Updated] (SOLR-3641) CoreContainer suspicious use of "roles"

[ https://issues.apache.org/jira/browse/SOLR-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-3641: -- Component/s: SolrCloud > CoreContainer suspicious use of "roles" > -

[jira] [Commented] (SOLR-3539) rethink softCommit=true|false param on commits?

[ https://issues.apache.org/jira/browse/SOLR-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442603#comment-13442603 ] Mark Miller commented on SOLR-3539: --- I agree we could clean this up. I worry about flush

Re: RecursivePrefixTreeFieldType class not found

Hi Dan, That page is the in-progress documentation for this: https://issues.apache.org/jira/browse/SOLR-3304 which hasn't been committed and so it requires you check out Lucene/Solr and apply the patch. The class reference will be solr.SpatialRecursivePrefixTreeFieldType. I updated the wiki.

[jira] [Commented] (SOLR-3539) rethink softCommit=true|false param on commits?

[ https://issues.apache.org/jira/browse/SOLR-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442617#comment-13442617 ] Hoss Man commented on SOLR-3539: bq. I worry about flush since it used to mean something el

[jira] [Commented] (SOLR-3512) Create API for managing nodes within SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442624#comment-13442624 ] Mark Miller commented on SOLR-3512: --- {quote}one is that it creates a reliance on the ZK c

[jira] [Assigned] (SOLR-3512) Create API for managing nodes within SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller reassigned SOLR-3512: - Assignee: Mark Miller > Create API for managing nodes within SolrCloud > -

[jira] [Updated] (LUCENE-4324) extend checkJavaDocs.py to methods,constants,fields

[ https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4324: Attachment: LUCENE-4324_crawl.patch the start to the patch that just crawls classes. Whenever we f

[jira] [Created] (LUCENE-4331) XXXDocValuesField javadocs are confusing about storing

Robert Muir created LUCENE-4331: --- Summary: XXXDocValuesField javadocs are confusing about storing Key: LUCENE-4331 URL: https://issues.apache.org/jira/browse/LUCENE-4331 Project: Lucene - Core

[jira] [Updated] (SOLR-3288) audit tutorial/example before 4.0 release

[ https://issues.apache.org/jira/browse/SOLR-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-3288: --- Description: Prior to the 4.0 release, audit the tutorial & example dirs and verify... * command line output

[jira] [Commented] (LUCENE-4331) XXXDocValuesField javadocs are confusing about storing

[ https://issues.apache.org/jira/browse/LUCENE-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442711#comment-13442711 ] Robert Muir commented on LUCENE-4331: - maybe we could disambiguate this somehow with

Re: Solr 4.0 Beta Documentation issues: Is it mandatory with 4.0 to run at least one core? /example/solr/README.txt needs updating

: 1) Is running at least one core required or is the message above referring : to some admin console functionality that wont work without at least one : core? If running at least one core is required, perhaps this needs also : to go in the Release notes/Changes. having at least one core (and ha

Re: Solr UIMA Notes

Hi Eric, 2012/8/10 Eric Pugh > Hi all, > > I've been working through the SolrUIMA demo, and have some changes to > propose based on going through it to make the UIMA stuff more accessible to > a new user. Since JIRA is down, I thought I would email my notes to the > list and see if anyone can c

[jira] [Commented] (SOLR-3488) Create a Collections API for SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442757#comment-13442757 ] Lance Norskog commented on SOLR-3488: - bq. Yeah, a work queue in ZK makes perfect sense

Re: Solr UIMA Notes

I recently went through a similar exercise with adding a large suite of stuff to Lucene & Solr. Strangely, it is for OpenNLP, another natural-language-processing toolkit. 2) Test of Lucene code from Solr unit tests. The problem is that the Lucene code requires a bunch of configuration. To write a

[jira] [Updated] (LUCENE-4324) extend checkJavaDocs.py to methods,constants,fields

[ https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-4324: --- Attachment: LUCENE-4322.patch I think it's working! > extend checkJ

[jira] [Resolved] (SOLR-3745) SolrCore should fail to init in SolrCloud mode if schema does not contain _version_ field

[ https://issues.apache.org/jira/browse/SOLR-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man resolved SOLR-3745. Resolution: Fixed Committed revision 1377898. - trunk Committed revision 1377899. - 4x I couldn't figure ou

Test coverage or "testing the tests"

Hi all At my current $DAYJOB we have been having a bit of success with an alternative coverage tool called pit-test ( http://pitest.org/). Essentially pit-test is a mutation testing tool that attempts to see how well the unit tests are able to catch alterations and regressions in the code that the

[jira] [Commented] (LUCENE-4324) extend checkJavaDocs.py to methods,constants,fields

[ https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442796#comment-13442796 ] Robert Muir commented on LUCENE-4324: - Thanks Mike! Some comments: {noformat} -

[jira] [Commented] (LUCENE-4324) extend checkJavaDocs.py to methods,constants,fields

[ https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442797#comment-13442797 ] Robert Muir commented on LUCENE-4324: - some small buglets in the output: {noformat} .

[jira] [Commented] (LUCENE-4324) extend checkJavaDocs.py to methods,constants,fields

[ https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442798#comment-13442798 ] Michael McCandless commented on LUCENE-4324: Oh yeah I'll nuke those changes

Re: Test coverage or "testing the tests"

This is cool. I'd say lets get it up and going on jenkins (even weekly or something). why worry about the imperfections in any of these coverage tools, whats way more important is when the results find situations where you thought you were testing something, but really arent, etc (here was a recent

Re: Test coverage or "testing the tests"

: This is cool. I'd say lets get it up and going on jenkins (even weekly : or something). why worry about the imperfections in any of these : coverage tools, whats way more important is when the results find : situations where you thought you were testing something, but really +1. Even if it ham

[jira] [Commented] (LUCENE-4324) extend checkJavaDocs.py to methods,constants,fields

[ https://issues.apache.org/jira/browse/LUCENE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442841#comment-13442841 ] Robert Muir commented on LUCENE-4324: - like the other javadoc checker tools this is p

Re: Test coverage or "testing the tests"

On 27/08/12 17:30, Chris Hostetter wrote: > : This is cool. I'd say lets get it up and going on jenkins (even weekly > : or something). why worry about the imperfections in any of these > : coverage tools, whats way more important is when the results find > : situations where you thought you were t

[JENKINS] Lucene-Solr-Tests-4.x-Java6 - Build # 542 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-Java6/542/ No tests ran. Build Log: [...truncated 4449 lines...] FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.Request

[jira] [Created] (LUCENE-4332) Integrate PiTest mutation coverage tool into build

Greg Bowyer created LUCENE-4332: --- Summary: Integrate PiTest mutation coverage tool into build Key: LUCENE-4332 URL: https://issues.apache.org/jira/browse/LUCENE-4332 Project: Lucene - Core Issu

[jira] [Updated] (LUCENE-4332) Integrate PiTest mutation coverage tool into build

[ https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Bowyer updated LUCENE-4332: Attachment: LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch > Integrate

Re: Test coverage or "testing the tests"

Ok first cut at a version of this in the build https://issues.apache.org/jira/browse/LUCENE-4332 On 27/08/12 18:05, Greg Bowyer wrote: > On 27/08/12 17:30, Chris Hostetter wrote: >> : This is cool. I'd say lets get it up and going on jenkins (even weekly >> : or something). why worry about the imp

[jira] [Updated] (LUCENE-4332) Integrate PiTest mutation coverage tool into build

[ https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Bowyer updated LUCENE-4332: Attachment: LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch Corrected jcomma

[jira] [Updated] (SOLR-3763) Make solr use lucene filters directly

[ https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Bowyer updated SOLR-3763: -- Description: Presently solr uses bitsets, queries and collectors to implement the concept of filters. T

[jira] [Created] (SOLR-3763) Make solr use lucene filters directly

Greg Bowyer created SOLR-3763: - Summary: Make solr use lucene filters directly Key: SOLR-3763 URL: https://issues.apache.org/jira/browse/SOLR-3763 Project: Solr Issue Type: Improvement Affect

[jira] [Reopened] (LUCENE-3923) fail the build on wrong svn:eol-style

[ https://issues.apache.org/jira/browse/LUCENE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reopened LUCENE-3923: --- Assignee: Uwe Schindler I have a new patch, which is very fast without custom task.

[jira] [Updated] (SOLR-3763) Make solr use lucene filters directly

[ https://issues.apache.org/jira/browse/SOLR-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Bowyer updated SOLR-3763: -- Attachment: SOLR-3763-Make-solr-use-lucene-filters-directly.patch Initial version, this has some hacks i

[jira] [Updated] (LUCENE-3923) fail the build on wrong svn:eol-style

[ https://issues.apache.org/jira/browse/LUCENE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-3923: -- Attachment: LUCENE-3923.patch The attached task fixes the slowness problem on windows and ASF

[jira] [Commented] (LUCENE-3923) fail the build on wrong svn:eol-style

[ https://issues.apache.org/jira/browse/LUCENE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442998#comment-13442998 ] Uwe Schindler commented on LUCENE-3923: --- The patch also fixes some other problems w