[jira] [Commented] (LUCENE-4397) TestIndexWriterWithThreads.testRollbackAndCommitWithThreads is sometimes very very slow

[ https://issues.apache.org/jira/browse/LUCENE-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13458225#comment-13458225 ] Jack Krupansky commented on LUCENE-4397: My latest test for branch_4x finished

[jira] [Commented] (LUCENE-4362) ban tab-indented source

[ https://issues.apache.org/jira/browse/LUCENE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457059#comment-13457059 ] Jack Krupansky commented on LUCENE-4362: Is this issue for 5.0 only or for 4.0 as

[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=13457513#comment-13457513 ] Jack Krupansky commented on SOLR-3823: -- bq. ...this is how subqueries have always

[jira] [Commented] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457520#comment-13457520 ] Jack Krupansky commented on SOLR-3729: -- I concur that the patch is insufficient.

[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=13455831#comment-13455831 ] Jack Krupansky commented on SOLR-3823: -- bq. bq is parsed with the defType specified

[jira] [Comment Edited] (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=13455831#comment-13455831 ] Jack Krupansky edited comment on SOLR-3823 at 9/15/12 1:59 AM:

[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=13455856#comment-13455856 ] Jack Krupansky commented on LUCENE-4369: At this stage of the discussion, is

[jira] [Comment Edited] (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=13455856#comment-13455856 ] Jack Krupansky edited comment on LUCENE-4369 at 9/15/12 2:14 AM:

[jira] [Commented] (LUCENE-3005) Define Test Plan for 4.0

[ https://issues.apache.org/jira/browse/LUCENE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455951#comment-13455951 ] Jack Krupansky commented on LUCENE-3005: That Lucid link doesn't work for me. I

[jira] [Commented] (LUCENE-4387) Eclipse classpath inconsistent with changes - Project fails to build

[ https://issues.apache.org/jira/browse/LUCENE-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455976#comment-13455976 ] Jack Krupansky commented on LUCENE-4387: Eclipse build works fine for me. I just

[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

[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 - Firefox as well (was: Google Chrome, Windows 7) Issue

[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] [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] (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] (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] [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-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-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-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] [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-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] [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=13435921#comment-13435921 ] Jack Krupansky commented on SOLR-3589: -- bq. It's not just mm. You set q.op to AND and

[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=13436045#comment-13436045 ] Jack Krupansky commented on SOLR-3589: -- bq. If I use a smart Chinese tokenizer to

[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=13436082#comment-13436082 ] Jack Krupansky commented on SOLR-3589: -- Be careful not to confuse dismax and edismax.

[jira] [Commented] (SOLR-2649) MM ignored in edismax queries with operators

[ https://issues.apache.org/jira/browse/SOLR-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13436088#comment-13436088 ] Jack Krupansky commented on SOLR-2649: -- I just ran a test with 4.0-BETA and it turns

[jira] [Commented] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435223#comment-13435223 ] Jack Krupansky commented on SOLR-3729: -- I verified with 3.6.1 that the problem exists

[jira] [Commented] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435226#comment-13435226 ] Jack Krupansky commented on SOLR-3729: -- Jan, since the SOLR-3377 fix didn't make it

[jira] [Commented] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435232#comment-13435232 ] Jack Krupansky commented on SOLR-3729: -- It is also worth noting that the basic

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Attachment: SOLR-3729.patch Patch for 4x branch, with tests. Tested in Eclipse. Haven't done full

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Fix Version/s: 4.0 ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[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=13435558#comment-13435558 ] Jack Krupansky commented on SOLR-3589: -- The root problem is that with automatic phrase

[jira] [Commented] (SOLR-3636) edismax, synonyms and mm=100%

[ https://issues.apache.org/jira/browse/SOLR-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435631#comment-13435631 ] Jack Krupansky commented on SOLR-3636: -- I checked the code, both in 4x and 3.6, and it

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

[ https://issues.apache.org/jira/browse/SOLR-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434253#comment-13434253 ] Jack Krupansky commented on SOLR-3441: -- It would be nice if this could be committed.

[jira] [Created] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

Jack Krupansky created SOLR-3729: Summary: ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly Key: SOLR-3729 URL: https://issues.apache.org/jira/browse/SOLR-3729 Project: Solr

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Description: I just happen to notice that (\*:\*) is not parsed properly by the edismax

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Description: I just happen to notice that (\*:\*) is not parsed properly by the edismax

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Description: I just happen to notice that (\*:\*) is not parsed properly by the edismax

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Description: I just happen to notice that (\*:\*) is not parsed properly by the edismax

[jira] [Updated] (SOLR-3729) ExtendedDismaxQParser (edismax) doesn't parse (*:*) properly

[ https://issues.apache.org/jira/browse/SOLR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3729: - Description: I just happen to notice that (\*:\*) is not parsed properly by the edismax

[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=13433774#comment-13433774 ] Jack Krupansky commented on SOLR-3377: -- Is this fixed for 3.6.2 as well? I would lobby

[jira] [Updated] (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:all-tabpanel ] Jack Krupansky updated SOLR-3377: - Comment: was deleted (was: Is this fixed for 3.6.2 as well? I would lobby for that since it is so

[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=13433784#comment-13433784 ] Jack Krupansky commented on SOLR-3377: -- Checking CHANGES.TXT and the revision history,

[jira] [Created] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

Jack Krupansky created SOLR-3723: Summary: Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true Key: SOLR-3723 URL: https://issues.apache.org/jira/browse/SOLR-3723

[jira] [Updated] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated SOLR-3723: - Description: Digging through the Jira and revision history, I discovered that back at the end of

[jira] [Commented] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431879#comment-13431879 ] Jack Krupansky commented on SOLR-3723: -- I intend to pore over the StandardTokenizer

[jira] [Commented] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431919#comment-13431919 ] Jack Krupansky commented on SOLR-3723: -- Mike, the English-specific field types that

[jira] [Commented] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432128#comment-13432128 ] Jack Krupansky commented on SOLR-3723: -- Uwe, by it's fine for pure english text did

[jira] [Commented] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432173#comment-13432173 ] Jack Krupansky commented on SOLR-3723: -- My current leaning is a mini-proposal as

[jira] [Comment Edited] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432173#comment-13432173 ] Jack Krupansky edited comment on SOLR-3723 at 8/9/12 9:31 PM: --

[jira] [Commented] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432214#comment-13432214 ] Jack Krupansky commented on SOLR-3723: -- Here is mini-report on my journey into

[jira] [Comment Edited] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432214#comment-13432214 ] Jack Krupansky edited comment on SOLR-3723 at 8/9/12 10:12 PM:

[jira] [Commented] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432244#comment-13432244 ] Jack Krupansky commented on SOLR-3723: -- Steven, yes, that's how I found the work break

[jira] [Comment Edited] (SOLR-3723) Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true

[ https://issues.apache.org/jira/browse/SOLR-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432214#comment-13432214 ] Jack Krupansky edited comment on SOLR-3723 at 8/9/12 10:41 PM:

[jira] [Commented] (SOLR-3703) Escape character which is in the query, is getting ignored in solr 3.6 with lucene parser

[ https://issues.apache.org/jira/browse/SOLR-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428244#comment-13428244 ] Jack Krupansky commented on SOLR-3703: -- You are probably being caught by the

[jira] [Commented] (LUCENE-4276) refuse to execute on broken corrupting jvms

[ https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425776#comment-13425776 ] Jack Krupansky commented on LUCENE-4276: What I would prefer to have is a

[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=13425853#comment-13425853 ] Jack Krupansky commented on SOLR-3580: -- I'm okay with the proposal for

[jira] [Commented] (SOLR-3672) SimplePostTool: Improvements for posting files

[ https://issues.apache.org/jira/browse/SOLR-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425426#comment-13425426 ] Jack Krupansky commented on SOLR-3672: -- Thanks for the great improvements, Jan. Only

[jira] [Commented] (SOLR-3439) 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=13420384#comment-13420384 ] Jack Krupansky commented on SOLR-3439: -- I haven't actually tried the new patch (and

[jira] [Commented] (SOLR-3619) Rename 'example' dir to 'server'

[ https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414562#comment-13414562 ] Jack Krupansky commented on SOLR-3619: -- Now I am confused. The summary seems

[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=13406796#comment-13406796 ] Jack Krupansky commented on SOLR-3377: -- This seems like a rather serious bug to me,

[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] [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-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] [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-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=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-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,

<    1   2   3   4   5   >