Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

whether or not it will be open source code #2

Open
jeromeheng opened this issue Jun 27, 2017 · 5 comments
Open

whether or not it will be open source code #2

jeromeheng opened this issue Jun 27, 2017 · 5 comments

Comments

@jeromeheng
Copy link

jeromeheng commented Jun 27, 2017

whether or not it will be open source code and how to use spark&postgresql to search database ?
i hope that you can answer me ,thanks !

@jeromeheng jeromeheng changed the title how whether or not it will be open source code Jun 27, 2017
@feiben
Copy link
Member

feiben commented Jun 27, 2017

Sure it will when its code gets solid and elegant. We have lots of comments to write for a better reading experience.

We are now trying to implement presto/hawq connectors for upper layer SQL support. And only the best one ( based on TPC-DH ) will be put in our roadmap of constant support. It's the top priority job now.

For the lunar-node project, it is opensource now. But in this very beginning stage, we focus on performance and stability. Code structure may change frequently. It is expected within two months, our team will release a stable version.

@jeromeheng
Copy link
Author

@feiben
Very good,I'm looking forward to your release version , I will continue to focus it .
Thanks : )

@jeromeheng
Copy link
Author

jeromeheng commented Jun 28, 2017

@feiben
one more question, you compare to other product with your white paper , and do your know what another product was used in olap&oltp ,just like mdrill 、druid 、ydb 、tindex and so on 。
How is it different with them ?

@feiben
Copy link
Member

feiben commented Jun 28, 2017

To my knowledge, any db-like things can be connected to a sql-engine, therefor it is capable of providing OLAP service at least. Most of the sql-engines support ANSI-SQL.

But the key is the throughput. A well designed engine provides quick enough response to whatever query push down to it., which is what we tried best to.

The engines you mentioned have their own advantages in specific domains. All of them claim their power of doing things. But for industrial decision-driven tasks, as TPC-DH that mentioned above, they may not support well. There is no official report on this.

I have no idea what they will behave on TPCH and TPC-DH at present.

@jeromeheng
Copy link
Author

@feiben
Thanks for your answer !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants