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

TreasureData getSchema fails when setting non-default region #3185

Closed
ksukenoda opened this issue Dec 12, 2018 · 2 comments · Fixed by #4582
Closed

TreasureData getSchema fails when setting non-default region #3185

ksukenoda opened this issue Dec 12, 2018 · 2 comments · Fixed by #4582

Comments

@ksukenoda
Copy link

Issue Summary

There are some regions in Treasure Data, but getSchema alsways fails when setting non-default region.

Steps to Reproduce

  1. Set datasource using non-default region (e.g. Tokyo region)
  2. Push schema refresh then "Schema refresh failed" error occurs

Technical details:

  • Redash Version: confirmed v5.0.2
  • Browser/OS: any Browsers/OSs
  • How did you install Redash: from Amazon AMI

Details

When accessing Treasure Data to get schema, always default region will be set because the parameter is not prepared.

redash/redash/query_runner/treasuredata.py

Line 82 in 6c36436

with tdclient.Client(self.configuration.get('apikey')) as client:

@ksukenoda
Copy link
Author

Treasure Data team will take care of this.

@arikfr
Copy link
Member

arikfr commented Dec 15, 2018

Treasure Data team will take care of this.

Thanks!

@mickeey2525 mickeey2525 mentioned this issue Jan 23, 2020
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix treasuredata endpoint mickeey2525/redash
2 participants
@arikfr @ksukenoda