You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2018/07/16 23:06:00 UTC

[jira] [Commented] (DRILL-6584) Implementing bitmap Indexes

    [ https://issues.apache.org/jira/browse/DRILL-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545845#comment-16545845 ] 

Kunal Khatua commented on DRILL-6584:
-------------------------------------

[~mehran] can you share your request on the dev mailing list? (dev@drill.apache.org)
This JIRA system is more useful in reporting bugs, but your question is asking specifically about guidelines. You'll likely find more responses there than here.

> Implementing bitmap Indexes
> ---------------------------
>
>                 Key: DRILL-6584
>                 URL: https://issues.apache.org/jira/browse/DRILL-6584
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Query Planning &amp; Optimization
>            Reporter: mehran
>            Priority: Major
>
> I see that you may have priorities in your development.
> and supporting multiple plugins for drill connections are also appreciated.
> But your default storage engine is parquet, that is very cool for its kind of purposes.
> Is it possible to bring forward implementing an index( roaring bitmap indexes similar to druid)?
> or just to write a guideline for developing index on drill?
> In fact full scan problems of drill is one of big problems that if solved, drill will be the best sql engine that can replace many use cases of databases.
>  
> Thank you in advance.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)