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

Jack Krupansky

[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-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-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-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] (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-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] (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] [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] (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] [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] (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-3534) dismax and edismax should default to df when qf is absent.

[ https://issues.apache.org/jira/browse/SOLR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293073#comment-13293073 ] Jack Krupansky commented on SOLR-3534: -- I would also suggest that the default if

[jira] [Commented] (SOLR-3534) dismax and edismax should default to df when qf is absent.

[ https://issues.apache.org/jira/browse/SOLR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293111#comment-13293111 ] Jack Krupansky commented on SOLR-3534: -- Okay, but if df does not have a default value,

[jira] [Commented] (SOLR-3534) dismax and edismax should default to df when qf is absent.

[ https://issues.apache.org/jira/browse/SOLR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293651#comment-13293651 ] Jack Krupansky commented on SOLR-3534: -- Looks like a reasonable compromise. I would

[jira] [Commented] (LUCENE-2605) queryparser parses on whitespace

[ https://issues.apache.org/jira/browse/LUCENE-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293748#comment-13293748 ] Jack Krupansky commented on LUCENE-2605: My thought on the original issue is that

[jira] [Commented] (SOLR-3535) Add block support for XMLLoader

[ https://issues.apache.org/jira/browse/SOLR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294504#comment-13294504 ] Jack Krupansky commented on SOLR-3535: -- Maybe there should be a block-doc-aware

[jira] [Commented] (SOLR-3534) dismax and edismax should default to df when qf is absent.

[ https://issues.apache.org/jira/browse/SOLR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295900#comment-13295900 ] Jack Krupansky commented on SOLR-3534: -- I think it would be helpful to users and ease

[jira] [Commented] (SOLR-2724) Deprecate defaultSearchField and defaultOperator defined in schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295907#comment-13295907 ] Jack Krupansky commented on SOLR-2724: -- As with SOLR-3534, I think it would be helpful

[jira] [Commented] (SOLR-2724) Deprecate defaultSearchField and defaultOperator defined in schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393389#comment-13393389 ] Jack Krupansky commented on SOLR-2724: -- Sounds good. At leat to me, but I already know

[jira] [Comment Edited] (SOLR-2724) Deprecate defaultSearchField and defaultOperator defined in schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393389#comment-13393389 ] Jack Krupansky edited comment on SOLR-2724 at 6/17/12 2:00 PM:

[jira] [Commented] (SOLR-2724) Deprecate defaultSearchField and defaultOperator defined in schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393548#comment-13393548 ] Jack Krupansky commented on SOLR-2724: -- I agree that we should encourage

[jira] [Commented] (SOLR-3580) In ExtendedDismax, lowercase 'not' operator is not being treated as an operator when 'lowercaseOperators' is enabled

[ https://issues.apache.org/jira/browse/SOLR-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402826#comment-13402826 ] Jack Krupansky commented on SOLR-3580: -- My recommendation is to have an additional

[jira] [Commented] (SOLR-3996) Solr 4.0.0: problems with character '/' in fields names

[ https://issues.apache.org/jira/browse/SOLR-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485286#comment-13485286 ] Jack Krupansky commented on SOLR-3996: -- A couple of comments: 1. Slash introduces a

[jira] [Commented] (SOLR-3980) Incorporate lazily-loaded cores into core listings for clients

[ https://issues.apache.org/jira/browse/SOLR-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486540#comment-13486540 ] Jack Krupansky commented on SOLR-3980: -- Why should STATUS force a core load - in the

[jira] [Commented] (LUCENE-4271) Solr LocalParams for Lucene Query Parser

[ https://issues.apache.org/jira/browse/LUCENE-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499491#comment-13499491 ] Jack Krupansky commented on LUCENE-4271: I don't see anything wrong with

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

[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503003#comment-13503003 ] Jack Krupansky commented on SOLR-139: - Thanks! Support

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

[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504724#comment-13504724 ] Jack Krupansky commented on SOLR-139: - I just tried it and the feature does work as

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

[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505040#comment-13505040 ] Jack Krupansky commented on SOLR-139: - No apology necessary for the noise. I mean, none

[jira] [Commented] (SOLR-3377) eDismax: A fielded query wrapped by parens is not recognized

[ https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505453#comment-13505453 ] Jack Krupansky commented on SOLR-3377: -- Leonhard, your use case seems rather different

[jira] [Commented] (SOLR-4114) Collection API: Allow multiple shards from one collection on the same Solr server

[ https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505541#comment-13505541 ] Jack Krupansky commented on SOLR-4114: -- I certainly think of replica as a copy of the

[jira] [Commented] (SOLR-3377) eDismax: A fielded query wrapped by parens is not recognized

[ https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505623#comment-13505623 ] Jack Krupansky commented on SOLR-3377: -- Yes, it looks like a bug, but distinct from

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

[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506520#comment-13506520 ] Jack Krupansky commented on SOLR-139: - Oh, yeah, that. I actually was going to mention

[jira] [Commented] (SOLR-4141) EDismax: Strange combination of subqueries with parentheses

[ https://issues.apache.org/jira/browse/SOLR-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508836#comment-13508836 ] Jack Krupansky commented on SOLR-4141: -- Unfortunately, this is not a bug, but the way

[jira] [Commented] (SOLR-4141) EDismax: Strange combination of subqueries with parentheses

[ https://issues.apache.org/jira/browse/SOLR-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509725#comment-13509725 ] Jack Krupansky commented on SOLR-4141: -- Feel free to suggest an improvement to make

[jira] [Commented] (SOLR-4114) Collection API: Allow multiple shards from one collection on the same Solr server

[ https://issues.apache.org/jira/browse/SOLR-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510504#comment-13510504 ] Jack Krupansky commented on SOLR-4114: -- Definition of integration testing: A process

[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling

[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527187#comment-13527187 ] Jack Krupansky commented on SOLR-4030: -- bq. Now we fork Forking is understandable

[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling

[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527232#comment-13527232 ] Jack Krupansky commented on SOLR-4030: -- bq. if a contributor wishes to withdraw his

[jira] [Commented] (SOLR-4169) The test suite should consistently pass

[ https://issues.apache.org/jira/browse/SOLR-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530018#comment-13530018 ] Jack Krupansky commented on SOLR-4169: -- +1 Maybe especially problematic tests could

[jira] [Commented] (SOLR-4169) The test suite should consistently pass

[ https://issues.apache.org/jira/browse/SOLR-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530528#comment-13530528 ] Jack Krupansky commented on SOLR-4169: -- bq. But then what would unit tests for Solr

[jira] [Commented] (SOLR-3589) Edismax parser does not honor mm parameter if analyzer splits a token

[ https://issues.apache.org/jira/browse/SOLR-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13436454#comment-13436454 ] Jack Krupansky commented on SOLR-3589: -- My proposal is for edismax to set the Lucene

[jira] [Commented] (SOLR-3589) Edismax parser does not honor mm parameter if analyzer splits a token

[ https://issues.apache.org/jira/browse/SOLR-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13436484#comment-13436484 ] Jack Krupansky commented on SOLR-3589: -- I could back off and simply say that edismax

[jira] [Created] (SOLR-3739) ExtendedDismaxQParser (edismax) does not obey q.op for tokens split by an analyzer

Jack Krupansky created SOLR-3739: Summary: ExtendedDismaxQParser (edismax) does not obey q.op for tokens split by an analyzer Key: SOLR-3739 URL: https://issues.apache.org/jira/browse/SOLR-3739

[jira] [Created] (SOLR-3740) ExtendedDismaxQParser (edismax) does not obey q.op for parenthesized sub-queries

Jack Krupansky created SOLR-3740: Summary: ExtendedDismaxQParser (edismax) does not obey q.op for parenthesized sub-queries Key: SOLR-3740 URL: https://issues.apache.org/jira/browse/SOLR-3740

[jira] [Created] (SOLR-3741) ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators

Jack Krupansky created SOLR-3741: Summary: ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators Key: SOLR-3741 URL: https://issues.apache.org/jira/browse/SOLR-3741 Project:

[jira] [Updated] (SOLR-3740) ExtendedDismaxQParser (edismax) does not obey q.op for parenthesized sub-queries

[ https://issues.apache.org/jira/browse/SOLR-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3740: - Fix Version/s: 3.6.2 Description: For a query such as cat dog (fox bat fish) with q.op=AND,

[jira] [Commented] (SOLR-3741) ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators

[ https://issues.apache.org/jira/browse/SOLR-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13437514#comment-13437514 ] Jack Krupansky commented on SOLR-3741: -- There is in fact a use case where q.op should

[jira] [Comment Edited] (SOLR-3741) ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators

[ https://issues.apache.org/jira/browse/SOLR-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13437514#comment-13437514 ] Jack Krupansky edited comment on SOLR-3741 at 8/20/12 1:14 AM:

[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-tabpanelfocusedCommentId=13442367#comment-13442367 ] Jack Krupansky commented on SOLR-3761: -- Is there any chance that you inadvertently

[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-tabpanelfocusedCommentId=13442367#comment-13442367 ] Jack Krupansky edited comment on SOLR-3761 at 8/27/12 11:03 PM:

[jira] [Commented] (SOLR-3771) While using RSS indexing from Solr, we are getting error Caused by: java.net.UnknownHostException indexing fail.

[ https://issues.apache.org/jira/browse/SOLR-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444978#comment-13444978 ] Jack Krupansky commented on SOLR-3771: -- Is there any specific reason why you believe

[jira] [Commented] (SOLR-3771) While using RSS indexing from Solr, we are getting error Caused by: java.net.UnknownHostException indexing fail.

[ https://issues.apache.org/jira/browse/SOLR-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445389#comment-13445389 ] Jack Krupansky commented on SOLR-3771: -- Any support questions should be directed to

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

[ https://issues.apache.org/jira/browse/SOLR-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445623#comment-13445623 ] Jack Krupansky commented on SOLR-3441: -- Thanks for the commit! Make

[jira] [Commented] (SOLR-3775) Unexpected RuntimeException

[ https://issues.apache.org/jira/browse/SOLR-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445886#comment-13445886 ] Jack Krupansky commented on SOLR-3775: -- Thanks for reporting the issue. Although it is

[jira] [Commented] (SOLR-3786) upload log without a version causes updates to silently fail.

[ https://issues.apache.org/jira/browse/SOLR-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448001#comment-13448001 ] Jack Krupansky commented on SOLR-3786: -- That bug fix missed 4.0-BETA by 11 days. The

[jira] [Commented] (SOLR-3786) upload log without a version causes updates to silently fail.

[ https://issues.apache.org/jira/browse/SOLR-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448069#comment-13448069 ] Jack Krupansky commented on SOLR-3786: -- The need to add the _version_ field to

[jira] [Created] (SOLR-3821) Solr Admin Query form is missing the default search field (df) request parameter

Jack Krupansky created SOLR-3821: Summary: Solr Admin Query form is missing the default search field (df) request parameter Key: SOLR-3821 URL: https://issues.apache.org/jira/browse/SOLR-3821

[jira] [Created] (SOLR-3822) Solr Admin Query form does not have hover titles for the edismax request parameters

Jack Krupansky created SOLR-3822: Summary: Solr Admin Query form does not have hover titles for the edismax request parameters Key: SOLR-3822 URL: https://issues.apache.org/jira/browse/SOLR-3822

[jira] [Commented] (LUCENE-4369) StringFields name is unintuitive and not helpful

[ https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13452998#comment-13452998 ] Jack Krupansky commented on LUCENE-4369: I would suggest RawTextField. Or,

[jira] [Commented] (SOLR-3823) Parentheses in a boost query cause errors

[ https://issues.apache.org/jira/browse/SOLR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453421#comment-13453421 ] Jack Krupansky commented on SOLR-3823: -- It turns out that it is the white space that

[jira] [Created] (LUCENE-4376) Add Query subclasses for selecting documents where a field is empty or not

Jack Krupansky created LUCENE-4376: -- Summary: Add Query subclasses for selecting documents where a field is empty or not Key: LUCENE-4376 URL: https://issues.apache.org/jira/browse/LUCENE-4376

[jira] [Updated] (LUCENE-4376) Add Query subclasses for selecting documents where a field is empty or not

[ https://issues.apache.org/jira/browse/LUCENE-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated LUCENE-4376: --- Issue Type: Improvement (was: Bug) Add Query subclasses for selecting documents where

[jira] [Commented] (LUCENE-4376) Add Query subclasses for selecting documents where a field is empty or not

[ https://issues.apache.org/jira/browse/LUCENE-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453558#comment-13453558 ] Jack Krupansky commented on LUCENE-4376: I don't see how the filter from

[jira] [Commented] (LUCENE-4376) Add Query subclasses for selecting documents where a field is empty or not

[ https://issues.apache.org/jira/browse/LUCENE-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453570#comment-13453570 ] Jack Krupansky commented on LUCENE-4376: Okay, so would it be straightforward and

[jira] [Created] (LUCENE-4382) Unicode escape no longer works for non-prefix wildcard terms

Jack Krupansky created LUCENE-4382: -- Summary: Unicode escape no longer works for non-prefix wildcard terms Key: LUCENE-4382 URL: https://issues.apache.org/jira/browse/LUCENE-4382 Project: Lucene -

[jira] [Updated] (LUCENE-4382) Unicode escape no longer works for non-prefix wildcard terms

[ https://issues.apache.org/jira/browse/LUCENE-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated LUCENE-4382: --- Description: LUCENE-588 added support for escaping of wildcard characters, but when the

[jira] [Updated] (LUCENE-4382) Unicode escape no longer works for non-suffix-only wildcard terms

[ https://issues.apache.org/jira/browse/LUCENE-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated LUCENE-4382: --- Description: LUCENE-588 added support for escaping of wildcard characters, but when the

[jira] [Created] (LUCENE-4386) Query parser should generate FieldValueFilter for pure wildcard terms to boost query performance

Jack Krupansky created LUCENE-4386: -- Summary: Query parser should generate FieldValueFilter for pure wildcard terms to boost query performance Key: LUCENE-4386 URL:

[jira] [Commented] (LUCENE-4386) Query parser should generate FieldValueFilter for pure wildcard terms to boost query performance

[ https://issues.apache.org/jira/browse/LUCENE-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455343#comment-13455343 ] Jack Krupansky commented on LUCENE-4386: I took Uwe's we can not automate this

[jira] [Commented] (LUCENE-4386) Query parser should generate FieldValueFilter for pure wildcard terms to boost query performance

[ https://issues.apache.org/jira/browse/LUCENE-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455346#comment-13455346 ] Jack Krupansky commented on LUCENE-4386: I would also note that the Javadoc for

[jira] [Created] (SOLR-3838) Multiple filter queries are not supported in the Solr Admin Query UI

Jack Krupansky created SOLR-3838: Summary: Multiple filter queries are not supported in the Solr Admin Query UI Key: SOLR-3838 URL: https://issues.apache.org/jira/browse/SOLR-3838 Project: Solr

[jira] [Created] (SOLR-3839) Query parser selection should be radio buttons rather than check boxes in Solr Admin Query UI

Jack Krupansky created SOLR-3839: Summary: Query parser selection should be radio buttons rather than check boxes in Solr Admin Query UI Key: SOLR-3839 URL: https://issues.apache.org/jira/browse/SOLR-3839

[jira] [Commented] (SOLR-3838) Multiple filter queries are not supported in the Solr Admin Query UI

[ https://issues.apache.org/jira/browse/SOLR-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455370#comment-13455370 ] Jack Krupansky commented on SOLR-3838: -- Note: The bq parameter has the same issue. I

[jira] [Created] (SOLR-3840) XML query response display is unreadable in Solr Admin Query UI

Jack Krupansky created SOLR-3840: Summary: XML query response display is unreadable in Solr Admin Query UI Key: SOLR-3840 URL: https://issues.apache.org/jira/browse/SOLR-3840 Project: Solr

[jira] [Commented] (SOLR-3811) Search Form does not set defType when dismax/edismax boxes are checked

[ https://issues.apache.org/jira/browse/SOLR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455399#comment-13455399 ] Jack Krupansky commented on SOLR-3811: -- I did in fact look at the other params and

[jira] [Updated] (SOLR-3840) XML query response display is unreadable in Solr Admin Query UI

[ https://issues.apache.org/jira/browse/SOLR-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3840: - Attachment: Query-UI-XML-unreadable.png I'm running Google Chrome on Windows 7. I attached the

[jira] [Updated] (SOLR-3840) XML query response display is unreadable in Solr Admin Query UI

[ https://issues.apache.org/jira/browse/SOLR-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3840: - Environment: Google Chrome, Windows 7 XML query response display is unreadable in Solr Admin

[jira] [Created] (SOLR-3841) Solr Admin Dashboard UI is completely dysfunctional on IE 9

Jack Krupansky created SOLR-3841: Summary: Solr Admin Dashboard UI is completely dysfunctional on IE 9 Key: SOLR-3841 URL: https://issues.apache.org/jira/browse/SOLR-3841 Project: Solr

[jira] [Updated] (SOLR-3841) Solr Admin Dashboard UI is completely dysfunctional on IE 9

[ https://issues.apache.org/jira/browse/SOLR-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3841: - Attachment: Solr-Dashboard-Empty.png Solr Admin Dashboard UI is completely dysfunctional on

  1   2   3   4   5   >