[
https://issues.apache.org/jira/browse/GORA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262757#comment-13262757
]
Ferdy Galema commented on GORA-119:
-----------------------------------
Hey Keith,
I like your idea about QueryOptimizer! I was struggling a bit on my own about
how to cleanly design the filter interface so that the optimization is coupled
with the implementation of the filter itself. Your suggestion exactly does
that! And indeed has the additional benefit of allowing users to implement
optimizers for their own filters. Only thing is that when implementing a
QueryOptimizer, a user might not want to be bothered with implementing the
generic non-optimized variant. (Not that it matters much, they could leave it
empty of course since it is a locally implemented filter). A slightly bigger
issue is that the Gora-supplied filters have knowledge about stores.
(Dependency inversion?). But then again we could simply leave the optimization
empty so that is up to each store to implement optimizations for those filters.
About the list of filters, this can easily be implemented with a Gora-supplied
filter that accepts a list with optional an operater (i.e. AND, OR).
Thanks.
> implement a filter enabled scan in gora
> ---------------------------------------
>
> Key: GORA-119
> URL: https://issues.apache.org/jira/browse/GORA-119
> Project: Apache Gora
> Issue Type: Improvement
> Affects Versions: 0.2
> Environment: gora hbase gora-core gora-hbase
> Reporter: raf shin
> Labels: filter, gora-core, gora-hbase, scan
> Fix For: 0.3
>
> Attachments: GORA-119-v1.txt
>
>
> it'll be very of help to implement a filtered scan to reduce the time of scan
> in gora-core and gora-hbase components.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
