-
Notifications
You must be signed in to change notification settings - Fork 36
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.
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
Gazer failing to Export Dashboards #244
Comments
Please note the host url with a little change to mark its real one |
What version of gzr are you running? |
@drstrangelooker I run this command and it says it successfully installed , gem install gazer Ruby version is ruby 3.2.3 (2024-01-18 revision 52bb2ac0a6) [x64-mingw-ucrt] But the error still here --------- error still here |
@drstrangelooker |
Hey @drstrangelooker |
I still don't have an answer. There were some changes to this code from 3.10 to 3.14 so I would have expected the latest version to work. Still investigating. |
Thanks @drstrangelooker Looking forward to your magic, |
If you can run this with version 0.3.14 and the |
Hey @drstrangelooker
|
Hey @drstrangelooker |
Hwy @drstrangelooker |
Hi @drstrangelooker By the way My colleague found for whatever reasons, the dashboard is still working but it is kind of corrupted. Then we add all those tiles on the dashboard in problem to the new Dashboard then re-link those dashboard filters. We have to use the new dashboard then export it and import it to all other instances. |
I haven't found an underlying issue that I can duplicate, so it is probably some sort of corruption or weird state in your instance. |
Thanks for trying!
…On Fri, 10 May 2024 at 00:13, Dr. Strangelove ***@***.***> wrote:
I haven't found an underlying issue that I can duplicate, so it is
probably some sort of corruption or weird state in your instance.
—
Reply to this email directly, view it on GitHub
<#244 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXLCLLR2FEYJI2SRLZP2PPLZBN77FAVCNFSM6AAAAABGBPASLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSG42DGNBVGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
------------------------------
*Qiang Du*
Business Intelligence Engineer
*E:* ***@***.***
*P:* 02 8005 5711
*W:* www.jobadder.com
[image: -]
[image: Twitter] <https://twitter.com/jobadder> [image: LinkedIn]
<https://www.linkedin.com/company/jobadder-com> [image: Instagram]
<https://www.instagram.com/jobadder/> [image: Facebook]
<https://www.facebook.com/JobAdder/>
[image: awards]
|
Hi, I am @jondu2022's colleague. Adding few more points from my end.
Fix needs to be on Gazer end to be able to pass the query slug instead of the query id to be able to export dashboards. We heavily use Gazer for our promotion management. We have releases planned in the near future and getting this fixed will help us immensely. Thanks |
Hi there, Adding more information based on the investigation of the code. Experts, please advise if my understanding is incorrect. Export fails for dashboards having merged queries.
I have contacted Looker support team checking if there is a way we could extract the query slug using a query id via an API call or add query slug information to the Get merge query API call. They are yet to get back to me. This issue might not exist with Looker hosted Looker instances as they have the option of turning off the legacy feature. Happy for the experts to share their insights on this issue and advise if there are any ways of fixing this issue for customer hosted looker instances. Thanks |
I'm looking right now. We recently pushed a patch to handle query slugs instead of ids. The code tries to use a slug, then falls back to a query id if the slug fails. |
Can you tell me what version of looker you are running? I have checked this case here and it is working properly. |
Hi @drstrangelooker , Can you please check if you can find this in legacy features of your Looker instance Admin - Legacy For information - we are not looker hosted looker instance and hence do not see the legacy feature to toggle off. It is turned on by default - which means Get Query APi end point will only accept query slugs and merge query API end point only gives query ids. We are on Looker version 24.0.39 Thanks |
Can you upgrade to 24.0.72 and try again? |
I confirmed that the code needed to get the query_slug with the merge_query shows up starting in 24.0.43. So if you upgrade this will work properly. |
C:\Users\username>gzr space export 1093 --host myhosturl: --no-verify-ssl --zip demo.zip
Error querying query(12345)
(GET https://myhosturl:19999/api/4.0/queries/12345: 404 - Not found
// See: https://cloud.google.com/looker/docs/r/err/4.0/404/get/queries/:query_id
// And: https://marketplace-api.looker.com/errorcodes/404.md)
I find there is a zip file generated in my local folder however, there is No dashboard json file, I only see some Look json files and one folder json file,
by the way, when I run "gzr user me" with the same host below, it is working fine.
Please advise
The text was updated successfully, but these errors were encountered: