lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uri Boness (JIRA)" <>
Subject [jira] Commented: (SOLR-1298) FunctionQuery results as pseudo-fields
Date Sun, 13 Dec 2009 15:47:18 GMT


Uri Boness commented on SOLR-1298:

I like the idea of giving the providing a broader context (document, request, response). This
will also allow them to operate on multiple documents in the response (whether it's the docset
or the doclist).

One thing to take into consideration here is that one you introduce dependency between the
fields, there must be a way to determine the ordering of the providers (as one provider might
depend on fields generated by another provider).

as for the "<field> AS <alias>" syntax. I think this should be consistent with
the work in SOLR-1351 which is currently based on localparams. Perhaps there should be a common
approach to handle aliases in requests.

I think that the proper approach is to separate the stored fields from other "fields.. perhaps
even put it in a separate "meta-data" section under the document. But once you do that, again,
for the sake of consistency, it would also be wise *not* to include these fields/functions
in the "fl" parameter. So the "fl" parameter will refer to fields, and another parameter "meta"
will refer to meta-data values.

bq. fl={!func}foo
+1 or even func:foo. Then you can have things like "url:<url>" or "file:<file path>"
or even "db:<db alias + field>"

> FunctionQuery results as pseudo-fields
> --------------------------------------
>                 Key: SOLR-1298
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 1.5
>         Attachments: SOLR-1298-FieldValues.patch, SOLR-1298.patch
> It would be helpful if the results of FunctionQueries could be added as fields to a document.

> Couple of options here:
> 1. Run FunctionQuery as part of relevance score and add that piece to the document
> 2. Run the function (not really a query) during Document/Field retrieval

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message