[jira] [Commented] (SOLR-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828791#comment-16828791 ] ASF subversion and git services commented on SOLR-4647: --- Commit a877632aaf86f5eeeba50201e7974f3329f5ccb9 in lucene-solr's branch refs/heads/branch_8x from Ishan Chattopadhyaya [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a877632 ] SOLR-12248, SOLR-4647: Grouping is broken on docValues-only fields > Grouping is broken on docvalues-only fields > --- > > Key: SOLR-4647 > URL: https://issues.apache.org/jira/browse/SOLR-4647 > Project: Solr > Issue Type: Bug > Components: search >Affects Versions: 4.2 >Reporter: Adrien Grand >Priority: Major > Labels: newdev > Attachments: SOLR-4647.patch > > > There are a few places where grouping uses > FieldType.toObject(SchemaField.createField(String, float)) to translate a > String field value to an Object. The problem is that createField returns null > when the field is neither stored nor indexed, even if it has doc values. > An option to fix it could be to use the ValueSource instead to resolve the > Object value (similarily to NumericFacets). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828789#comment-16828789 ] ASF subversion and git services commented on SOLR-4647: --- Commit 4b49bd99ca20cee2263a3cd3c115c7d00b98f043 in lucene-solr's branch refs/heads/master from Ishan Chattopadhyaya [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=4b49bd9 ] SOLR-12248, SOLR-4647: Grouping is broken on docValues-only fields > Grouping is broken on docvalues-only fields > --- > > Key: SOLR-4647 > URL: https://issues.apache.org/jira/browse/SOLR-4647 > Project: Solr > Issue Type: Bug > Components: search >Affects Versions: 4.2 >Reporter: Adrien Grand >Priority: Major > Labels: newdev > Attachments: SOLR-4647.patch > > > There are a few places where grouping uses > FieldType.toObject(SchemaField.createField(String, float)) to translate a > String field value to an Object. The problem is that createField returns null > when the field is neither stored nor indexed, even if it has doc values. > An option to fix it could be to use the ValueSource instead to resolve the > Object value (similarily to NumericFacets). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061877#comment-14061877 ] Modassar Ather commented on SOLR-4647: -- Hi, I am also seeing this issue while doing grouping on docValues enabled field. I checked createField(...) method of FieldType which returns null if the field is not indexed and stored. Kindly provide inputs if any of the indexe/stored needs to be set to true while creating a docValue field or this is an issue. Thanks, Modassar Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867009#comment-13867009 ] Iker Huerga commented on SOLR-4647: --- Hi, I've been able to replicate the issue which I think happens when stored=false in schema.xml for the DocValue field type. I could start working on a patch for it if nobody else is already working on it. Thanks Iker Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [jira] [Commented] (SOLR-4647) Grouping is broken on docvalues-only fields
Hi,
think I hit that problem. Create a schema with normal fields (e.g. id)
and an DocValues field (e.g. feature). If you want to get the DocValues
field value (/select?q=id:123fl=feature) no value is returned.
Setting the DocValues field stored=true or false doesn't change
anything. The value is not returned.
We worked around that by using an own Field implementation that
programmatically set the stored flag true:
public class OwnDocValuesField extends Field {
public static final FieldType TYPE = new FieldType();
static {
TYPE.setDocValueType(FieldInfo.DocValuesType.BINARY);
//set to true, so we are able to retrieve the docvalues via fl
parameter
TYPE.setStored(true);
TYPE.freeze();
}
public OwnDocValuesField(String name, BytesRef value) {
super(name, TYPE);
fieldsData = value;
}
}
We use this class in an own FieldType implementation. I guess our
problem is caused by the issue described in SOLR-4647.
I cannot estimate if this is a bug or if DocValues works as designed,
and simply should not be used this way. Does anyone know that?
lg
Sebastian
Am 24.06.2013 16:20, schrieb Subashini Soundararajan (JIRA):
[
https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692007#comment-13692007
]
Subashini Soundararajan commented on SOLR-4647:
hi I'm a newbie, can someone please provide additional context about the
issue/ways to reproduce it?
Thanks!
Grouping is broken on docvalues-only fields
---
Key: SOLR-4647
URL: https://issues.apache.org/jira/browse/SOLR-4647
Project: Solr
Issue Type: Bug
Affects Versions: 4.2
Reporter: Adrien Grand
Labels: newdev
There are a few places where grouping uses
FieldType.toObject(SchemaField.createField(String, float)) to translate a
String field value to an Object. The problem is that createField returns
null when the field is neither stored nor indexed, even if it has doc values.
An option to fix it could be to use the ValueSource instead to resolve the
Object value (similarily to NumericFacets).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
--
M. Sc. Sebastian Müller
CTO
phone: +49(0)30 60984960
email: muel...@pixolution.de
* pixolution @ Microstock Expo, 16th and 17th November 2013 in Berlin *
pixolution GmbH | Sprungschanzenweg 90 | 14169 Berlin
HRB 120049 | www.pixolution.de | Follow us on LinkedIn
Geschäftsführung / executive board:
Prof. Dr. Kai-Uwe Barthel | Sebastian Müller | Michael M. Rost
Confidentiality: This e-mail contains confidential information intended
only for the addressee. If you are not the intended recipient you may
not disclose, copy, use or otherwise distribute the content of this email.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4647) Grouping is broken on docvalues-only fields
[
https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692831#comment-13692831
]
Sebastian Müller commented on SOLR-4647:
think I hit that problem. Create a schema with normal fields (e.g. id)
and an DocValues field (e.g. feature). If you want to get the DocValues
field value (/select?q=id:123fl=feature) no value is returned.
Setting the DocValues field stored=true or false doesn't change
anything. The value is not returned.
We worked around that by using an own Field implementation that
programmatically set the stored flag true:
public class OwnDocValuesField extends Field {
public static final FieldType TYPE = new FieldType();
static {
TYPE.setDocValueType(FieldInfo.DocValuesType.BINARY);
//set to true, so we are able to retrieve the docvalues via fl
parameter
TYPE.setStored(true);
TYPE.freeze();
}
public OwnDocValuesField(String name, BytesRef value) {
super(name, TYPE);
fieldsData = value;
}
}
We use this class in an own FieldType implementation. I guess our
problem is caused by the issue described in SOLR-4647.
I cannot estimate if this is a bug or if DocValues works as designed,
and simply should not be used this way. Does anyone know that?
lg
Sebastian
Grouping is broken on docvalues-only fields
---
Key: SOLR-4647
URL: https://issues.apache.org/jira/browse/SOLR-4647
Project: Solr
Issue Type: Bug
Affects Versions: 4.2
Reporter: Adrien Grand
Labels: newdev
There are a few places where grouping uses
FieldType.toObject(SchemaField.createField(String, float)) to translate a
String field value to an Object. The problem is that createField returns null
when the field is neither stored nor indexed, even if it has doc values.
An option to fix it could be to use the ValueSource instead to resolve the
Object value (similarily to NumericFacets).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692007#comment-13692007 ] Subashini Soundararajan commented on SOLR-4647: hi I'm a newbie, can someone please provide additional context about the issue/ways to reproduce it? Thanks! Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623667#comment-13623667 ] David Smiley commented on SOLR-4647: There seems to be a need for a String-to-value method on FieldType. Based on the current method names, its signature should be Object toObject(String str). By default it could return str directly. Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623761#comment-13623761 ] Robert Muir commented on SOLR-4647: --- Also i think there is a need for at least trivial tests of grouping against docvalues fields! Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623965#comment-13623965 ] Yonik Seeley commented on SOLR-4647: It should be really easy to add docvalues based fields to TestGroupingSearch.testRandomGrouping Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4647) Grouping is broken on docvalues-only fields
[ https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615967#comment-13615967 ] David Arthur commented on SOLR-4647: I ran into this as well. For me, grouping was working for int fields, but not string fields. Here is the exception I got: https://gist.github.com/mumrah/7d87999e59cfa716f045 Grouping is broken on docvalues-only fields --- Key: SOLR-4647 URL: https://issues.apache.org/jira/browse/SOLR-4647 Project: Solr Issue Type: Bug Affects Versions: 4.2 Reporter: Adrien Grand Labels: newdev There are a few places where grouping uses FieldType.toObject(SchemaField.createField(String, float)) to translate a String field value to an Object. The problem is that createField returns null when the field is neither stored nor indexed, even if it has doc values. An option to fix it could be to use the ValueSource instead to resolve the Object value (similarily to NumericFacets). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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
