[ https://issues.apache.org/jira/browse/DRILL-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949393#comment-15949393 ]
Laurent Goujon commented on DRILL-5402: --------------------------------------- Like I mentioned in the pull request for DRILL-3510, I haven't seen this feature implemented by other JDBC drivers, so this might get some sense regarding priority. Another thing to consider I believe is that the servermeta object is big (contains all the function names for example), with these functions not changing. So from a protocol point of view, instead of forcing the user to call again {{GetServerMeta}}, user could request just the session, and the driver might combine both the metadata and the session to return the final value? or maybe extend GetServerMeta api with a flag to only return some of the fields? > ServerMeta should be updated during the session, if the last has been changed. > ------------------------------------------------------------------------------ > > Key: DRILL-5402 > URL: https://issues.apache.org/jira/browse/DRILL-5402 > Project: Apache Drill > Issue Type: Improvement > Components: Client - Java, Client - ODBC, Execution - RPC, Metadata > Affects Versions: 1.10.0 > Reporter: Vitalii Diravka > Assignee: Vitalii Diravka > Priority: Minor > Fix For: 1.11.0 > > > DRILL-5301 introduces a new server metadata API. > But clients can get from the server the current meta information only once, > the next request returns the previous meta even if it was updated. For > example, Identifier quote character can be changed by the user via one > session. > It would be good if the session is changed, the "getServerMeta()" will return > updated server meta information. -- This message was sent by Atlassian JIRA (v6.3.15#6346)