Skip to content

Conversation

@qqchang2nd
Copy link

Description:
Currently, HadoopTables.load() doesn't support passing custom properties when loading tables. While HiveCatalog and HadoopCatalog support manifest caching through their initialize() method (as implemented in #4518), HadoopTables lacks this capability. This enhancement adds property support to HadoopTables.load() to enable manifest caching and other configurations.

Problem:

  • HadoopTables lacks the ability to configure manifest caching during table loading
  • Unlike HiveCatalog and HadoopCatalog which can enable manifest caching through initialize(), HadoopTables has no mechanism to pass these settings
  • This creates inconsistency in how manifest caching can be configured across different catalog implementations

Description:
Currently, HadoopTables.load() doesn't support passing custom properties when loading tables.
While HiveCatalog and HadoopCatalog support manifest caching through their initialize() method
(as implemented in apache#4518), HadoopTables lacks this capability. This enhancement adds property
support to HadoopTables.load() to enable manifest caching and other configurations.

Problem:
- HadoopTables lacks the ability to configure manifest caching during table loading
- Unlike HiveCatalog and HadoopCatalog which can enable manifest caching through initialize(),
HadoopTables has no mechanism to pass these settings
- This creates inconsistency in how manifest caching can be configured across different catalog
implementations
@github-actions
Copy link

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 20, 2025
@qqchang2nd
Copy link
Author

This PR is ready for review, @rdblue Could you please review it?
Happy to address any feedback. Thanks for your time!

@github-actions github-actions bot removed the stale label Mar 22, 2025
@github-actions
Copy link

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 21, 2025
@github-actions
Copy link

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant