Skip to content

edit NAMESPACE_PROPERTY_KEY to not be a reserved SQL keyword#5017

Merged
rdblue merged 2 commits intoapache:masterfrom
sungwy:master
Jun 12, 2022
Merged

edit NAMESPACE_PROPERTY_KEY to not be a reserved SQL keyword#5017
rdblue merged 2 commits intoapache:masterfrom
sungwy:master

Conversation

@sungwy
Copy link
Copy Markdown
Contributor

@sungwy sungwy commented Jun 10, 2022

Issue reference:
#4952

@sungwy
Copy link
Copy Markdown
Contributor Author

sungwy commented Jun 10, 2022

@rdblue

Hi Ryan! Here's the PR to remediate the ANSI SQL reserved keyword conflict. I am opening the PR through my company email associated account in accordance with Open Source Contribution standards, as mentioned on the issue:
#4952

@rdblue
Copy link
Copy Markdown
Contributor

rdblue commented Jun 10, 2022

Running CI.

@sungwy
Copy link
Copy Markdown
Contributor Author

sungwy commented Jun 11, 2022

Hi @rdblue I fixed an issue where one of the sqlStatements was explicitly using "key" instead of NAMESPACE_PROPERTY_KEY.

Now all the tests are succeeding except for this particular one mentioned on this PR:
#4825

Task :iceberg-spark:iceberg-spark-3.2_2.12:test

1552 tests completed, 1 failed, 126 skipped

Task :iceberg-spark:iceberg-spark-3.2_2.12:test FAILED

testOlderThanTimestamp
java.lang.AssertionError: Should delete only 2 files expected:<2> but was:<3>

@rdblue
Copy link
Copy Markdown
Contributor

rdblue commented Jun 12, 2022

@syun64, I just merged the test fix. Running CI on this now. Thanks!

@rdblue rdblue merged commit c4cb017 into apache:master Jun 12, 2022
@rdblue
Copy link
Copy Markdown
Contributor

rdblue commented Jun 12, 2022

Thanks, @syun64!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants