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

Table always existed when using import vizard to import CSV file from S3 #4013

Open
1 task done
clarbase opened this issue Feb 24, 2025 · 0 comments
Open
1 task done
Labels
BUG Issue type for reporting failure due to bug in functionality

Comments

@clarbase
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Description

Hue Importer:

While using importer feature in Hue we are getting an error saying "Table already exist" even if the table does not exist.

Presto/Trino import to table:
The issue is also observed while trying to use "Import to table" option for Presto/Trino tables and for hive we are able to create new tables using import to table.

Does Trino/ Presto support "Import to table"?

Tested this behavior in multiple EMR versions with the most up to date Hue version and it does not work in any of them:
EMR 5.3, EMR 5.33, EMR 5.25, EMR 6.4, EMR 6.15, EMR 7.3

Steps To Reproduce

Image

  1. Sign in to the AWS Management Console and launch an EMR cluster of version5.30+ with Hue, Hive, Presto/Trino services https://console.aws.amazon.com/.

  2. Once the cluster is ready, login to Hue Ul by enabling SSH tunneling to master
    node.

Hue Importer
3. Now click on "Importer" located at the left hand side of the Hue options.

4.Now in Source select Type as "File" or "External Database".

  1. If the Type is selected as "File" pick a file from either from s3 or from HDFS and
    then click o n next.
    If the selected Type is "External Database" configure the database details and
    click on "NEXT"
    Refer below screenshot for reference

Logs

No response

Hue version

4.11

@clarbase clarbase added the BUG Issue type for reporting failure due to bug in functionality label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Issue type for reporting failure due to bug in functionality
Projects
None yet
Development

No branches or pull requests

1 participant