[
https://issues.apache.org/jira/browse/OPTIQ-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053263#comment-14053263
]
Jacques Nadeau commented on OPTIQ-333:
--------------------------------------
The problem with the current SPI is Drill's approach to implicitly created
tables as the user asks for them. I'm not sure that fits within what you would
traditionally consider for this SPI, thus our need to go a layer lower.
Let's define a contract and take this all the way because this has continued to
be pain point. What changes would you like to see to make this happen?
> Abstract OptiqSchema as a base class and move the existing implementation to
> a separate class
> ---------------------------------------------------------------------------------------------
>
> Key: OPTIQ-333
> URL: https://issues.apache.org/jira/browse/OPTIQ-333
> Project: Optiq
> Issue Type: Improvement
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
>
> The implementation of OptiqSchema can make users jump through many hoops
> because it holds a complex hold internal state. A couple of times now,
> efforts to move Apache Drill to newer versions of Optiq has required all
> schema management code to be rewritten as the nature of the internally
> maintained state has changed. As such, this JIRA is about abstracting out
> the core interface and providing an alternative, near stateless
> implementation. Existing tools will continue to leverage the traditional
> existing implementation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
