For reference, the SQL/JDBC piece needed ability to specify wildcard and
figure out the "schema" of the collection including defined dynamic fields.
When testing lately with supporting "select *" type semantics, it would be
nice to be able to limit to only DocValues fields.
The introspection for determining fields needed to hit all shards w/ the
luke request handler due to some shards maybe having a dynamic field in
them. The Schema API gives back only dynamic schema fields but not actually
which fields are present in the collection. SOLR-8823 has an implementation
that does the introspection if that helps.
Some related JIRAs:
- implement get columns for JDBC spec - SOLR-8823
- Calcite - SOLR-8593
- uses the same logic basically as SOLR-8823
Kevin Risden
On Thu, Nov 17, 2016 at 5:40 PM, Erick Erickson <[email protected]>
wrote:
> I looked through the JIRAs and didn't see anything relevant, but
> before raising a JIRA I thought I'd see if there was interest.
>
> In the case where there are dynamic fields, one may not know what all
> the fields that are DV fields. I think there's a use case for /export
> being able to accept wildcards, i.e. fl=* or fl=*_s. The idea would be
> that the handler would get the field list and pull in all the fields
> defined with docValues=true.
>
> I suppose that this would be most useful if I got busy and actually
> worked on SOLR-3191:"field exclusion from fl".
>
> It's not clear to me though how expensive the introspection would be
> though.
>
> Thoughts?
>
> Erick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
