Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add to connection init the ability to set the queue AND trigger an engine resource #173

Open
dstreev opened this issue Jan 23, 2025 · 0 comments
Open

Add to connection init the ability to set the queue AND trigger an engine resource #173

dstreev opened this issue Jan 23, 2025 · 0 comments
Assignees
@dstreev
Labels
enhancement New feature or request

Comments

@dstreev
Copy link
Collaborator

dstreev commented Jan 23, 2025

Connection validation currently doesn't test the queue OR ensures the client can spin up engine resources.

Adding the following to the connection initialization will ensure resource can be obtained.

 "SET hive.query.results.cache.enabled=false",
  "SET hive.fetch.task.conversion = none",
  "SELECT 1"
@dstreev dstreev added the enhancement New feature or request label Jan 23, 2025
@dstreev dstreev self-assigned this Jan 23, 2025
dstreev added a commit to dstreev/hms-mirror that referenced this issue Jan 24, 2025
@dstreev
**What's New**
39af71d 
BETA Iceberg conversion support for the STORAGE_MIGRATION data strategy. See [Iceberg Conversion](hms-mirror-iceberg_migration.md) for more details.

**Bugs (Fixed)**
[Add to connection init the ability to set the queue AND trigger an engine resource](cloudera-labs/hms-mirror#173)
[cloudera-labs/hms-mirror#168
Validate SQL elements before making changes to the Cluster](cloudera-labs/hms-mirror#168)
[Extend the HS2 connection validation with Tez task validation](cloudera-labs/hms-mirror#167)
[The reset-to-default-location doesn't seem to be working in v2](cloudera-labs/hms-mirror#165)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dstreev dstreev

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dstreev