[
https://issues.apache.org/jira/browse/SOLR-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894844#comment-13894844
]
Hoss Man commented on SOLR-5707:
--------------------------------
Hey Ryan,
Please forgive my ignorance of the expression stuff, but can you comment on
your choice to leverage them in Solr via this new "ComputedField" FieldType
instead of as a new implementation of ValueSourceParser ? (i'm trying to wrap
my head around if/why this "expression based psuedo-field declared in
schema.xml" idea is better then an "expression based psuedo-field declared at
request time via a function".)
bq. Note: I'm not happy with the difficulty in using custom xml children nodes
for a field type, but I didn't want to tackle that here.
Yeah ... rather then add more custom XML parsing + special method call hooks in
IndexSchema, we may want to consider biting the bullet and opening a new issue
to add a marker Interface any FieldType can use, and then TextField & your new
ComputedField can both implement...{code}
public interface FieldTypeThatSupportsComplexNestedXmlNodeIniti {
public void giveMeMyChildNodes(NodeList children) throws SolrException;
}
{code}...but i know sarowe is looking towards a future where more things in the
schema.xml can be programatically defined via APIs, so that would probably be a
step in the direction of giving him a heart attack.
> Lucene Expressions in Solr
> --------------------------
>
> Key: SOLR-5707
> URL: https://issues.apache.org/jira/browse/SOLR-5707
> Project: Solr
> Issue Type: New Feature
> Reporter: Ryan Ernst
> Attachments: SOLR-5707.patch
>
>
> Expressions should be available for use in Solr.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
