[jira] [Commented] (SOLR-3407) Field names with leading digits cause strange behavior when used with fl param
[ https://issues.apache.org/jira/browse/SOLR-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261582#comment-13261582 ] Mark Miller commented on SOLR-3407: --- We really should start enforcing the field names we allow IMO. Field names with leading digits cause strange behavior when used with fl param Key: SOLR-3407 URL: https://issues.apache.org/jira/browse/SOLR-3407 Project: Solr Issue Type: Bug Components: search Affects Versions: 4.0 Environment: apache-solr-4.0-2012-04-24_08-27-47 Reporter: Chris Bleakley When specifying a field name that starts with a digit (or digits) in the fl parameter solr returns both the field name and field value as the those digits. For example, using nightly build apache-solr-4.0-2012-04-24_08-27-47 I run: java -jar start.jar and java -jar post.jar solr.xml monitor.xml If I then add a field to the field list that starts with a digit ( localhost:8983/solr/select?q=*:*fl=24 ) the results look like: ... doc long name=2424/long /doc ... if I try fl=24_7 it looks like everything after the underscore is truncated ... doc long name=2424/long /doc ... and if I try fl=3test it looks like everything after the last digit is truncated ... doc long name=33/long /doc ... If I have an actual value for that field (say I've indexed 24_7 to be true ) I get back that value as well as the behavior above. ... doc bool name=24_7true/bool long name=2424/long /doc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3407) Field names with leading digits cause strange behavior when used with fl param
[ https://issues.apache.org/jira/browse/SOLR-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261585#comment-13261585 ] Mark Miller commented on SOLR-3407: --- bq. an unnecessary change that serves no purpose. What exactly is the change you are referring to? Field names with leading digits cause strange behavior when used with fl param Key: SOLR-3407 URL: https://issues.apache.org/jira/browse/SOLR-3407 Project: Solr Issue Type: Bug Components: search Affects Versions: 4.0 Environment: apache-solr-4.0-2012-04-24_08-27-47 Reporter: Chris Bleakley When specifying a field name that starts with a digit (or digits) in the fl parameter solr returns both the field name and field value as the those digits. For example, using nightly build apache-solr-4.0-2012-04-24_08-27-47 I run: java -jar start.jar and java -jar post.jar solr.xml monitor.xml If I then add a field to the field list that starts with a digit ( localhost:8983/solr/select?q=*:*fl=24 ) the results look like: ... doc long name=2424/long /doc ... if I try fl=24_7 it looks like everything after the underscore is truncated ... doc long name=2424/long /doc ... and if I try fl=3test it looks like everything after the last digit is truncated ... doc long name=33/long /doc ... If I have an actual value for that field (say I've indexed 24_7 to be true ) I get back that value as well as the behavior above. ... doc bool name=24_7true/bool long name=2424/long /doc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3407) Field names with leading digits cause strange behavior when used with fl param
[ https://issues.apache.org/jira/browse/SOLR-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261605#comment-13261605 ] Luca Cavanna commented on SOLR-3407: I guess this is a side effect coming from SOLR-2444. Solr already had similar problems (SOLR-2719: hyphen within the field name didn't work anymore). Some kind of validation would help (SOLR-3207) but it's not trivial to do since there are dynamic fields too; I think Solr should guarantee that allowed field names always work, or at least make clearer what restrictions there are. Field names with leading digits cause strange behavior when used with fl param Key: SOLR-3407 URL: https://issues.apache.org/jira/browse/SOLR-3407 Project: Solr Issue Type: Bug Components: search Affects Versions: 4.0 Environment: apache-solr-4.0-2012-04-24_08-27-47 Reporter: Chris Bleakley When specifying a field name that starts with a digit (or digits) in the fl parameter solr returns both the field name and field value as the those digits. For example, using nightly build apache-solr-4.0-2012-04-24_08-27-47 I run: java -jar start.jar and java -jar post.jar solr.xml monitor.xml If I then add a field to the field list that starts with a digit ( localhost:8983/solr/select?q=*:*fl=24 ) the results look like: ... doc long name=2424/long /doc ... if I try fl=24_7 it looks like everything after the underscore is truncated ... doc long name=2424/long /doc ... and if I try fl=3test it looks like everything after the last digit is truncated ... doc long name=33/long /doc ... If I have an actual value for that field (say I've indexed 24_7 to be true ) I get back that value as well as the behavior above. ... doc bool name=24_7true/bool long name=2424/long /doc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [jira] [Commented] (SOLR-3407) Field names with leading digits cause strange behavior when used with fl param
The change is that you can't specify a fl in 4.0 which works just fine in 3.6. If you specify a fl=24_7, even with a the field defined, your return in trunk now contains things like: result name=response numFound=38 start=0 doc long name=2424/long /doc doc even when there is no data in the 24_7 field and even though there's no such field as 24. Now, that said I think we _should_ create some kind of validator for field names, but it _has_ to have some back-compat. Forcing users to change their field names (and re-index _everything_ perhaps) shouldn't be done casually IMO. So if we do have some field-name validation we should be sensitive to this. Perhaps tie it in with the luceneMatchVersion? FWIW Erick P.S. Yes, this is one of my hot-buttons, but I suspect you already knew that G. On Wed, Apr 25, 2012 at 8:26 AM, Mark Miller (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/SOLR-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261585#comment-13261585 ] Mark Miller commented on SOLR-3407: --- bq. an unnecessary change that serves no purpose. What exactly is the change you are referring to? Field names with leading digits cause strange behavior when used with fl param Key: SOLR-3407 URL: https://issues.apache.org/jira/browse/SOLR-3407 Project: Solr Issue Type: Bug Components: search Affects Versions: 4.0 Environment: apache-solr-4.0-2012-04-24_08-27-47 Reporter: Chris Bleakley When specifying a field name that starts with a digit (or digits) in the fl parameter solr returns both the field name and field value as the those digits. For example, using nightly build apache-solr-4.0-2012-04-24_08-27-47 I run: java -jar start.jar and java -jar post.jar solr.xml monitor.xml If I then add a field to the field list that starts with a digit ( localhost:8983/solr/select?q=*:*fl=24 ) the results look like: ... doc long name=2424/long /doc ... if I try fl=24_7 it looks like everything after the underscore is truncated ... doc long name=2424/long /doc ... and if I try fl=3test it looks like everything after the last digit is truncated ... doc long name=33/long /doc ... If I have an actual value for that field (say I've indexed 24_7 to be true ) I get back that value as well as the behavior above. ... doc bool name=24_7true/bool long name=2424/long /doc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3407) Field names with leading digits cause strange behavior when used with fl param
[ https://issues.apache.org/jira/browse/SOLR-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261024#comment-13261024 ] Erick Erickson commented on SOLR-3407: -- This does NOT happen on 3.6, but DOES happen on trunk. Field names with leading digits cause strange behavior when used with fl param Key: SOLR-3407 URL: https://issues.apache.org/jira/browse/SOLR-3407 Project: Solr Issue Type: Bug Components: search Affects Versions: 4.0 Environment: apache-solr-4.0-2012-04-24_08-27-47 Reporter: Chris Bleakley When specifying a field name that starts with a digit (or digits) in the fl parameter solr returns both the field name and field value as the those digits. For example, using nightly build apache-solr-4.0-2012-04-24_08-27-47 I run: java -jar start.jar and java -jar post.jar solr.xml monitor.xml If I then add a field to the field list that starts with a digit ( localhost:8983/solr/select?q=*:*fl=24 ) the results look like: ... doc long name=2424/long /doc ... if I try fl=24_7 it looks like everything after the underscore is truncated ... doc long name=2424/long /doc ... and if I try fl=3test it looks like everything after the last digit is truncated ... doc long name=33/long /doc ... If I have an actual value for that field (say I've indexed 24_7 to be true ) I get back that value as well as the behavior above. ... doc bool name=24_7true/bool long name=2424/long /doc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3407) Field names with leading digits cause strange behavior when used with fl param
[ https://issues.apache.org/jira/browse/SOLR-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261159#comment-13261159 ] Erick Erickson commented on SOLR-3407: -- OK, but this means that perfectly valid schemas in 3.x do NOT work in trunk. Seems arbitrary and like a pettifogging change by arrogant devs. Sorry, but really this seems like an unnecessary change that serves no purpose. Field names with leading digits cause strange behavior when used with fl param Key: SOLR-3407 URL: https://issues.apache.org/jira/browse/SOLR-3407 Project: Solr Issue Type: Bug Components: search Affects Versions: 4.0 Environment: apache-solr-4.0-2012-04-24_08-27-47 Reporter: Chris Bleakley When specifying a field name that starts with a digit (or digits) in the fl parameter solr returns both the field name and field value as the those digits. For example, using nightly build apache-solr-4.0-2012-04-24_08-27-47 I run: java -jar start.jar and java -jar post.jar solr.xml monitor.xml If I then add a field to the field list that starts with a digit ( localhost:8983/solr/select?q=*:*fl=24 ) the results look like: ... doc long name=2424/long /doc ... if I try fl=24_7 it looks like everything after the underscore is truncated ... doc long name=2424/long /doc ... and if I try fl=3test it looks like everything after the last digit is truncated ... doc long name=33/long /doc ... If I have an actual value for that field (say I've indexed 24_7 to be true ) I get back that value as well as the behavior above. ... doc bool name=24_7true/bool long name=2424/long /doc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
