[
https://issues.apache.org/jira/browse/DRILL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605875#comment-13605875
]
Julian Hyde commented on DRILL-13:
----------------------------------
To expand on Jacques' comments. It's interesting to declare that a storage
engine supports bloom filters, but I don't think it's useful, because each
engine functions so differently. I think the code to push down bloom filters
would have to be written separately for each engine. The way I'd solve it for
Optiq would be to have a bloom filter rule for each engine.
To put it another way. The real use cases are "I want Drill to use bloom
filters to work against HBase" and "I want Drill to use bloom filters to work
against Cassandra". Log those as jira cases. Whoever fixes them can extend the
storage engine interface if they see fit. But my hunch is that they won't.
> Storage Engine: Define Java Interface
> -------------------------------------
>
> Key: DRILL-13
> URL: https://issues.apache.org/jira/browse/DRILL-13
> Project: Apache Drill
> Issue Type: Task
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
>
> We're going to need to define a storage engine API. At a minimum, we'll need
> to generate a Java one. We will probably need to also create a CPP one.
> This task is for the former. Things that are likely to be included in a the
> Java interface are: reader (scanner), writer, capabilities interface, schema
> interface, statistics interface, data layout and ordering
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
