On Fri, Nov 18, 2016 at 11:46 AM, Kevin Risden <[email protected]> wrote:
>> Out of curiosity, how is this used (and in what contexts)?
>> I'm wondering the implications of new fields appearing when new
>> documents are added. Will this mess up the JDBC driver?
>
>
> Currently its not being used. Select * isn't supported yet.
Does "select *" need to know ahead of time what fields there will be?
Although retrieving the set of stored fields (or the set of used
fields) should be easy to implement, it doesn't seem like the most
efficient way to implement things (at least at the streaming API
level..)
If we need to know the set of fields that match a wildcard before
streaming all of the documents, we could easily add that info
on-demand at the head (sort of like column headers).
So currently we have:
{
"response": {
"docs": [...]
}
}
And we could insert "fields" inside the response object:
{
"response": {
"fields":["field1","field2","field3","field4"]
"docs": [...]
}
}
Or alternately outside of the "response" object:
{
"fields":["field1","field2","field3","field4"],
"response": {
"docs": [...]
}
}
Or is there some reason we need the full set of fields before we even
send the request?
-Yonik
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
