[jira] [Commented] (SOLR-3416) HTTP ERROR 400. Problem accessing /solr/select/. Reason: undefined field text

[ https://issues.apache.org/jira/browse/SOLR-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290122#comment-13290122 ] Jack Krupansky commented on SOLR-3416: -- This is most certainly not a bug in Solr.

[jira] [Commented] (SOLR-3508) improve json update format

[ https://issues.apache.org/jira/browse/SOLR-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289475#comment-13289475 ] Jack Krupansky commented on SOLR-3508: -- To be clear, the intent is that the value of a

[jira] [Commented] (LUCENE-4115) JAR resolution/ cleanup should be done automatically for ant clean/ eclipse/ resolve.

[ https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289697#comment-13289697 ] Jack Krupansky commented on LUCENE-4115: The other case I was interested in is if

[jira] [Commented] (LUCENE-4115) JAR resolution/ cleanup should be done automatically for ant clean/ eclipse/ resolve.

[ https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289715#comment-13289715 ] Jack Krupansky commented on LUCENE-4115: Sounds good. Just to be sure I followed

[jira] [Commented] (LUCENE-4114) Large docID / docvalue size combination produces arithmetic overflow

[ https://issues.apache.org/jira/browse/LUCENE-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289772#comment-13289772 ] Jack Krupansky commented on LUCENE-4114: There may be a similar bug at line 345:

[jira] [Commented] (LUCENE-4114) Large docID / docvalue size combination produces arithmetic overflow

[ https://issues.apache.org/jira/browse/LUCENE-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289775#comment-13289775 ] Jack Krupansky commented on LUCENE-4114: Sorry, the latter case is probably okay

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288164#comment-13288164 ] Jack Krupansky commented on LUCENE-4101: Superficially, the new concept of a

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288167#comment-13288167 ] Jack Krupansky commented on SOLR-3503: -- It could be tricky, but it could work, but

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288174#comment-13288174 ] Jack Krupansky commented on SOLR-3503: -- Or are you just trying to trick me into doing

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288202#comment-13288202 ] Jack Krupansky commented on SOLR-3503: -- Ultimately it may simply come down to doing

[jira] [Created] (LUCENE-4104) Clearly document the limit for maximum number of documents in a single index

Jack Krupansky created LUCENE-4104: -- Summary: Clearly document the limit for maximum number of documents in a single index Key: LUCENE-4104 URL: https://issues.apache.org/jira/browse/LUCENE-4104

[jira] [Commented] (LUCENE-4104) Clearly document the limit for maximum number of documents in a single index

[ https://issues.apache.org/jira/browse/LUCENE-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288263#comment-13288263 ] Jack Krupansky commented on LUCENE-4104: I propose to add these constants to

[jira] [Updated] (LUCENE-4104) Clearly document the limit for maximum number of documents in a single index

[ https://issues.apache.org/jira/browse/LUCENE-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated LUCENE-4104: --- Description: Although the int in a number of APIs strongly suggests the approximate limit

[jira] [Created] (SOLR-3504) Clearly document the limit for the maximum number of documents in a single index

Jack Krupansky created SOLR-3504: Summary: Clearly document the limit for the maximum number of documents in a single index Key: SOLR-3504 URL: https://issues.apache.org/jira/browse/SOLR-3504

[jira] [Commented] (SOLR-3504) Clearly document the limit for the maximum number of documents in a single index

[ https://issues.apache.org/jira/browse/SOLR-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288266#comment-13288266 ] Jack Krupansky commented on SOLR-3504: -- Solr has a number of interfaces for adding

[jira] [Created] (LUCENE-4105) Detect and report when the limit for maximum number of documents in a single index is exceeded

Jack Krupansky created LUCENE-4105: -- Summary: Detect and report when the limit for maximum number of documents in a single index is exceeded Key: LUCENE-4105 URL:

[jira] [Created] (SOLR-3505) Detect and report when the limit for maximum number of documents in a single index is exceeded

Jack Krupansky created SOLR-3505: Summary: Detect and report when the limit for maximum number of documents in a single index is exceeded Key: SOLR-3505 URL: https://issues.apache.org/jira/browse/SOLR-3505

[jira] [Commented] (LUCENE-4105) Detect and report when the limit for maximum number of documents in a single index is exceeded

[ https://issues.apache.org/jira/browse/LUCENE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288274#comment-13288274 ] Jack Krupansky commented on LUCENE-4105: To facilitate testing, I would propose

[jira] [Commented] (SOLR-3505) Detect and report when the limit for maximum number of documents in a single index is exceeded

[ https://issues.apache.org/jira/browse/SOLR-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288277#comment-13288277 ] Jack Krupansky commented on SOLR-3505: -- Similar to LUCENE-4105, it would greatly

[jira] [Updated] (SOLR-3502) [Copy Field][Importing] Copy Field duplicate a field and a multivalued field can be created without having field multivalued in schema

[ https://issues.apache.org/jira/browse/SOLR-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3502: - Attachment: SOLR-3502-4x.patch I can repro the problem in 3.6. The essence is that the copyField

[jira] [Commented] (SOLR-3500) ERROR Unable to execute query

[ https://issues.apache.org/jira/browse/SOLR-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13287462#comment-13287462 ] Jack Krupansky commented on SOLR-3500: -- Doesn't sound like a Solr bug. Take it over to

[jira] [Commented] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285112#comment-13285112 ] Jack Krupansky commented on SOLR-3439: -- Thinking about the overall intent of example,

[jira] [Commented] (LUCENE-4081) JVM outOfMemory when call IndexWriter.optimize() method

[ https://issues.apache.org/jira/browse/LUCENE-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284610#comment-13284610 ] Jack Krupansky commented on LUCENE-4081: Doesn't sound like a bug. Take the issue

[jira] [Commented] (SOLR-3489) Config file replication less error prone

[ https://issues.apache.org/jira/browse/SOLR-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13283485#comment-13283485 ] Jack Krupansky commented on SOLR-3489: -- It would be nice to add a similar protection

[jira] [Commented] (SOLR-3455) WordDelimiterFilterFactory split word on hyphen though generateWordParts=0

[ https://issues.apache.org/jira/browse/SOLR-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277878#comment-13277878 ] Jack Krupansky commented on SOLR-3455: -- Given this configuration, 34333 should only

[jira] [Commented] (SOLR-3455) WordDelimiterFilterFactory split word on hyphen though generateWordParts=0

[ https://issues.apache.org/jira/browse/SOLR-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277930#comment-13277930 ] Jack Krupansky commented on SOLR-3455: -- It still doesn't sound as if there is an

[jira] [Commented] (SOLR-3466) org.apache.solr.common.SolrException: org.apache.lucene.queryParser.ParseException: Cannot parse

[ https://issues.apache.org/jira/browse/SOLR-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278064#comment-13278064 ] Jack Krupansky commented on SOLR-3466: -- Please resubmit your inquiry over on the

[jira] [Commented] (SOLR-3466) org.apache.solr.common.SolrException: org.apache.lucene.queryParser.ParseException: Cannot parse

[ https://issues.apache.org/jira/browse/SOLR-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278081#comment-13278081 ] Jack Krupansky commented on SOLR-3466: -- Review:

[jira] [Commented] (SOLR-2058) Adds optional phrase slop to edismax pf2, pf3 and pf parameters with field~slop^boost syntax

[ https://issues.apache.org/jira/browse/SOLR-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278202#comment-13278202 ] Jack Krupansky commented on SOLR-2058: -- It would be nice to have a user-friendly error

[jira] [Commented] (SOLR-3461) TestRealTimeGet.testStressRecovery() is sometimes very slow on Windows, using al CPUs

[ https://issues.apache.org/jira/browse/SOLR-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277230#comment-13277230 ] Jack Krupansky commented on SOLR-3461: -- It runs reasonably on my Windows 7 i5-based

[jira] [Commented] (SOLR-3461) TestRealTimeGet.testStressRecovery() is sometimes very slow on Windows, using al CPUs

[ https://issues.apache.org/jira/browse/SOLR-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277269#comment-13277269 ] Jack Krupansky commented on SOLR-3461: -- With the change, the test went from 130

[jira] [Commented] (SOLR-2058) Adds optional phrase slop to edismax pf2, pf3 and pf parameters with field~slop^boost syntax

[ https://issues.apache.org/jira/browse/SOLR-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276322#comment-13276322 ] Jack Krupansky commented on SOLR-2058: -- Just a question: Is it 100% compatible with

[jira] [Commented] (SOLR-3442) Example schema switch to DisMax instead of CopyField

Jack Krupansky

[jira] [Commented] (SOLR-3442) Example schema switch to DisMax instead of CopyField

[ https://issues.apache.org/jira/browse/SOLR-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269584#comment-13269584 ] Jack Krupansky commented on SOLR-3442: -- Maybe Solr has outgrown the concept of a

[jira] [Commented] (SOLR-3442) Example schema switch to DisMax instead of CopyField

[ https://issues.apache.org/jira/browse/SOLR-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269794#comment-13269794 ] Jack Krupansky commented on SOLR-3442: -- bq. The lucene query parser generally

[jira] [Commented] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269803#comment-13269803 ] Jack Krupansky commented on SOLR-3439: -- Based on the discussion here and on SOLR-3442,

[jira] [Commented] (LUCENE-4024) FuzzyQuery should never do edit distance 2

[ https://issues.apache.org/jira/browse/LUCENE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269913#comment-13269913 ] Jack Krupansky commented on LUCENE-4024: bq. The levenshtein distance has changed

[jira] [Commented] (LUCENE-4024) FuzzyQuery should never do edit distance 2

[ https://issues.apache.org/jira/browse/LUCENE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269951#comment-13269951 ] Jack Krupansky commented on LUCENE-4024: I updated svn and see the Javadoc now. A

[jira] [Issue Comment Edited] (LUCENE-4024) FuzzyQuery should never do edit distance 2

[ https://issues.apache.org/jira/browse/LUCENE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269951#comment-13269951 ] Jack Krupansky edited comment on LUCENE-4024 at 5/7/12 8:07 PM:

[jira] [Updated] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3439: - Attachment: Lincoln-Gettysburg-Address.pdf Lincoln-Gettysburg-Address.docx Test

[jira] [Commented] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269244#comment-13269244 ] Jack Krupansky commented on SOLR-3439: -- We could have the copyFields default to being

[jira] [Commented] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269247#comment-13269247 ] Jack Krupansky commented on SOLR-3439: -- Right, so if it is the double indexing that is

[jira] [Updated] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3439: - Attachment: SOLR-3439.patch Preliminary patch. content is both stored and indexed, with multiple

[jira] [Created] (SOLR-3441) Make ElisionFilterFactory MultiTermAware

Jack Krupansky created SOLR-3441: Summary: Make ElisionFilterFactory MultiTermAware Key: SOLR-3441 URL: https://issues.apache.org/jira/browse/SOLR-3441 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-3441) Make ElisionFilterFactory MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3441: - Attachment: SOLR-3441.patch Preliminary patch. Make ElisionFilterFactory

[jira] [Commented] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269326#comment-13269326 ] Jack Krupansky commented on SOLR-3439: -- The concept of copyField is implicitly a

[jira] [Created] (SOLR-3438) Document SolrCells' use of the meta field

Jack Krupansky created SOLR-3438: Summary: Document SolrCells' use of the meta field Key: SOLR-3438 URL: https://issues.apache.org/jira/browse/SOLR-3438 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-3438) Document SolrCells' use of the meta field

[ https://issues.apache.org/jira/browse/SOLR-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3438: - Attachment: SolrCell meta field.xml I added two files via SolrCell, a Word doc (.docx) and a PDF

[jira] [Updated] (SOLR-3438) Document SolrCell's use of the meta field

[ https://issues.apache.org/jira/browse/SOLR-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3438: - Description: SolrCell will add document metadata to the field named meta if it is present in the

[jira] [Updated] (SOLR-3438) Document SolrCell's use of the meta field

[ https://issues.apache.org/jira/browse/SOLR-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3438: - Attachment: SolrCell meta field.xml Forgot to format with indent. Document

[jira] [Created] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

Jack Krupansky created SOLR-3439: Summary: Add content field to example schema to make SolrCell easier to use out of the box Key: SOLR-3439 URL: https://issues.apache.org/jira/browse/SOLR-3439

[jira] [Created] (SOLR-3440) CLONE - dismax and edismax should treate schema's default field as a default qf

Jack Krupansky created SOLR-3440: Summary: CLONE - dismax and edismax should treate schema's default field as a default qf Key: SOLR-3440 URL: https://issues.apache.org/jira/browse/SOLR-3440 Project:

[jira] [Updated] (SOLR-3440) CLONE - dismax and edismax should treate schema's default field as a default qf

[ https://issues.apache.org/jira/browse/SOLR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3440: - Fix Version/s: (was: 4.0) (was: 3.1) Priority: Minor (was:

[jira] [Commented] (SOLR-3439) Add content field to example schema to make SolrCell easier to use out of the box

[ https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269103#comment-13269103 ] Jack Krupansky commented on SOLR-3439: -- I'll post a preliminary patch tomorrow.

<    1   2   3   4   5