These are chat archives for getredash/redash

20th
Sep 2016
Neil Shah
@shahneil88
Sep 20 2016 03:15
This message was deleted
Neil Shah
@shahneil88
Sep 20 2016 03:29
I modified some code in manage.py and models.py to replicate #1253 When I tried to execute CLI, I receive error [2016-09-20 11:14:33,274][PID:4376][ERROR][peewee] SELECT "t1"."id", "t1"."updated_at", "t1"."created_at", "t1"."name", "t1"."slug", "t1"."settings" FROM "organizations" AS t1 WHERE ("t1"."slug" = %s) LIMIT 1 [u'default'] Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/playhouse/postgres_ext.py", line 360, in execute_sql cursor.execute(sql, params or ()) ProgrammingError: relation "organizations" does not exist LINE 1: ...", "t1"."name", "t1"."slug", "t1"."settings" FROM "organizat...
@arikfr @WesleyBatista - But, I do see that I already have organizations table in my redash metadata
Neil Shah
@shahneil88
Sep 20 2016 03:55
I checked a bit and it seems running sudo -u redash bin/run ./manage.py database create_tables might solve the issue. Would it affect my existing redash setup?
Arik Fraimovich
@arikfr
Sep 20 2016 04:43
Yes, it will
What version of Redash do you have?
Neil Shah
@shahneil88
Sep 20 2016 05:33
@arikfr - 0.11.1+b2095
Arik Fraimovich
@arikfr
Sep 20 2016 05:34
then the table should already exist.
Neil Shah
@shahneil88
Sep 20 2016 05:34
Yes, I can see the table
But, it still give me this error
Arik Fraimovich
@arikfr
Sep 20 2016 05:34
are you sure you ran the command with sudo -u redash bin/run prefix the first time?
Neil Shah
@shahneil88
Sep 20 2016 05:34
No
I actually ran sudo python manage.py queries fork 56
Arik Fraimovich
@arikfr
Sep 20 2016 05:35
well that's the problem
Neil Shah
@shahneil88
Sep 20 2016 05:35
Sorry, sudo -u redash python manage.py queries fork 56
Arik Fraimovich
@arikfr
Sep 20 2016 05:35
still
you need bin/run as well
Neil Shah
@shahneil88
Sep 20 2016 05:35
oh ok
Let me give it a try
Is this the correct way? sudo -u redash bin/run manage.py queries fork 56 @arikfr
Neil Shah
@shahneil88
Sep 20 2016 05:42
Ok. It worked. Thank you for your help :)
Wesley
@WesleyBatista
Sep 20 2016 09:56
Good it worked! 😃
Neil Shah
@shahneil88
Sep 20 2016 10:35
Yes. Saved lot of time by using the script that you wrote @WesleyBatista :)
Jens Lukas
@jenslukas
Sep 20 2016 11:08
I am having difficulties with the API. I try to get updated results by making following POST request: /api/queries/38/refresh?api_key=XXXXX&p_nodeId=1220&p_startDate=2016-09-19&p_endDate=2016-09-20
as a result I receive following JSON response: {
"job": {
"status": 2,
"error": "",
"id": "162aa11e-ad87-46f7-b2fd-3204b00c0a87",
"query_result_id": null,
"updated_at": 0
}
}
but a call to /api/queries/38/results.json?api_key=XXXXX always returns old cached results
anyone knows what I might be doing wrong (running 0.11.0+b2016)
HenroRitchie
@HenroRitchie
Sep 20 2016 12:00
@arikfr When are you planning on releasing 0.12?