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
[WIP] HIVE-26628: Iceberg table is created when running explain ctas command #3670
Closed
kasakrisz
wants to merge
23
commits into
apache:master
from
kasakrisz:HIVE-26628-master-explain-iceberg-ctas
Closed
[WIP] HIVE-26628: Iceberg table is created when running explain ctas command #3670
kasakrisz
wants to merge
23
commits into
apache:master
from
kasakrisz:HIVE-26628-master-explain-iceberg-ctas
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kasakrisz
force-pushed
the
HIVE-26628-master-explain-iceberg-ctas
branch
from
October 19, 2022 11:08
a7e928b
to
d0fc361
Compare
kgyrtkirk
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
Oct 19, 2022
kasakrisz
force-pushed
the
HIVE-26628-master-explain-iceberg-ctas
branch
from
October 20, 2022 13:40
d0fc361
to
5960d7d
Compare
kgyrtkirk
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
Oct 20, 2022
kasakrisz
force-pushed
the
HIVE-26628-master-explain-iceberg-ctas
branch
from
October 21, 2022 13:39
5960d7d
to
09481cf
Compare
kgyrtkirk
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
Oct 21, 2022
kasakrisz
force-pushed
the
HIVE-26628-master-explain-iceberg-ctas
branch
from
October 24, 2022 15:33
09481cf
to
6c37c44
Compare
kgyrtkirk
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
Oct 24, 2022
kasakrisz
force-pushed
the
HIVE-26628-master-explain-iceberg-ctas
branch
from
October 25, 2022 11:39
6c37c44
to
be76101
Compare
kgyrtkirk
added
tests pending
tests passed
and removed
tests unstable
tests pending
labels
Oct 25, 2022
issue is fixed by #3745 |
…StorageHandler present
This reverts commit 6853773.
…toreConstants.TABLE_IS_CTAS)) reuse String tableIdentifier = catalogProperties.getProperty(Catalogs.NAME);
kasakrisz
force-pushed
the
HIVE-26628-master-explain-iceberg-ctas
branch
from
November 30, 2022 12:44
6a6b952
to
529ad73
Compare
kgyrtkirk
added
tests pending
tests failed
and removed
tests failed
tests pending
labels
Nov 30, 2022
fixed by #3802 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This patch is an attempt to refactor the way ctas is executed:
HiveIcebergSerDe
since it is also created at compile time.TezTask
to create the Iceberg table.Hive.getTranslateTableDryrun
Execution before this patch:
HiveIcebergSerDe - table creation
TezTask - run query and write datafiles
MoveTask- commit writes
Execution with this patch:
DDLTask - table creation
TezTask - run query and write datafiles
MoveTask- commit writes
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?