Andrew Wong created HUDI-614:
--------------------------------
Summary: .hoodie_partition_metadata created for non-partitioned
table
Key: HUDI-614
URL: https://issues.apache.org/jira/browse/HUDI-614
Project: Apache Hudi (incubating)
Issue Type: Bug
Reporter: Andrew Wong
Original issue: [https://github.com/apache/incubator-hudi/issues/1329]
I made a non-partitioned Hudi table using Spark. I was able to query it with
Spark & Hive, but when I tried querying it with Presto, I received the error
{{Could not find partitionDepth in partition metafile}}.
I attempted this task using emr-5.28.0 in AWS. I tried using the built-in
spark-shell with both Amazon's /usr/lib/hudi/hudi-spark-bundle.jar (following
[https://aws.amazon.com/blogs/aws/new-insert-update-delete-data-on-s3-with-amazon-emr-and-apache-hudi/)]
and the org.apache.hudi:hudi-spark-bundle_2.11:0.5.1-incubating jar (following
[https://hudi.apache.org/docs/quick-start-guide.html]).
I used NonpartitionedKeyGenerator & NonPartitionedExtractor in my write
options, according to
[https://cwiki.apache.org/confluence/display/HUDI/FAQ#FAQ-HowdoIuseDeltaStreamerorSparkDataSourceAPItowritetoaNon-partitionedHudidataset?].
You can see my code in the github issue linked above.
In both cases I see the .hoodie_partition_metadata file was created in the
table path in S3. Querying the table worked in spark-shell & hive-cli, but
attempting to query the table in presto-cli resulted in the error, "Could not
find partitionDepth in partition metafile".
Please look into the bug or check the documentation. If there is a problem with
the EMR install I can contact the AWS team responsible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
