[Improvement] Optimize Trino connector property mapping system #1455
Comments
yuqi1129
added a commit
that referenced
this issue
Jan 18, 2024
…property (#1458) ### What changes were proposed in this pull request? Use the new `PropertyConverter` in `catalog-common` to replace the old one. ### Why are the changes needed? We must provide a uniform property mapping system between Gravitino and the query engine. Fix: #1455 ### Does this PR introduce _any_ user-facing change? N/A. ### How was this patch tested? Existing test can cover this change.
mchades
pushed a commit
to mchades/gravitino
that referenced
this issue
Jan 19, 2024
…ngine property (apache#1458) ### What changes were proposed in this pull request? Use the new `PropertyConverter` in `catalog-common` to replace the old one. ### Why are the changes needed? We must provide a uniform property mapping system between Gravitino and the query engine. Fix: apache#1455 ### Does this PR introduce _any_ user-facing change? N/A. ### How was this patch tested? Existing test can cover this change.
mchades
pushed a commit
to mchades/gravitino
that referenced
this issue
Jan 24, 2024
…ngine property (apache#1458) ### What changes were proposed in this pull request? Use the new `PropertyConverter` in `catalog-common` to replace the old one. ### Why are the changes needed? We must provide a uniform property mapping system between Gravitino and the query engine. Fix: apache#1455 ### Does this PR introduce _any_ user-facing change? N/A. ### How was this patch tested? Existing test can cover this change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be improved?
Based on #1449 , we can optimize the current property mapping system to be more well-designed.
How should we improve?
No response
The text was updated successfully, but these errors were encountered: