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

[Feature] Support query hive table #6568

Closed
3 tasks done
qidaye opened this issue Sep 3, 2021 · 5 comments · Fixed by #6569
Closed
3 tasks done

[Feature] Support query hive table #6568

qidaye opened this issue Sep 3, 2021 · 5 comments · Fixed by #6569
Labels
area/extension/hive kind/feature Categorizes issue or PR as related to a new feature.

Comments

@qidaye
Copy link
Contributor

qidaye commented Sep 3, 2021

Search before asking

  • I had searched in the issues and found no similar issues.

Description

Currently, Hive external tables are only used by Spark Load, and queries are not supported.

Many users have the need to query the Hive table, and it is too cumbersome to import the data into Doris and then perform the query operation.

Use case

Users can directly query the data in the hive table in Doris, and can use join to perform complex queries without laboriously importing data from hive

Related issues

None.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@qidaye qidaye added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 3, 2021
@imay
Copy link
Contributor

imay commented Sep 13, 2021

Actually, this is a feature, and this feature will change usage interface. When this is merged, it is hard to changed any more, because a database should keep back compatible with old version.
I suggest that it will be better to add user interface to let people discuss.

@imay
Copy link
Contributor

imay commented Sep 13, 2021

I see a good case from Impala community, which I think we can refer.
The following mail list is about adding unnest feature.
https://lists.apache.org/thread.html/r1095fd324e65b8fbbc31b7da61a69367e08bbf5cb6fcd1fd9e72f133%40%3Cdev.impala.apache.org%3E

@qidaye qidaye changed the title [Proposal] Support query hive table [Feature] Support query hive table Sep 14, 2021
@qidaye
Copy link
Contributor Author

qidaye commented Sep 14, 2021

Actually, this is a feature

Thanks for pointing out.

this feature will change usage interface.

What do you mean? I'm a little confused.

With this feature, users can not only import Hive data to Doris olap table by Spark load, but also can query hive external table by Doris. These two funcitons dose not confict. It keeps back compatible with old versions.

@imay
Copy link
Contributor

imay commented Sep 14, 2021

Actually, this is a feature

Thanks for pointing out.

this feature will change usage interface.

What do you mean? I'm a little confused.

With this feature, users can not only import Hive data to Doris olap table by Spark load, but also can query hive external table by Doris. These two funcitons dose not confict. It keeps back compatible with old versions.

I think you misunderstand my point, what I want to say is that this issue will introduce new SQL interface, such as 'CREATE TABLE'. This needs to be disscussed before coding to avoid later modification.

@qidaye
Copy link
Contributor Author

qidaye commented Sep 14, 2021

this issue will introduce new SQL interface , such as 'CREATE TABLE'.

This issue does not introduce any new SQL interface.

We already have create hive external table syntax, which can see by command help create table.
What I intend to do is to implement the query hive external table. Dose not change any SQL interface.

You can see the create hive table syntax in the related PR, which is exactly the same as Doris' existing create hive external table statement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extension/hive kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants