These are chat archives for getredash/redash

1st
Dec 2014
Arik Fraimovich
@arikfr
Dec 01 2014 05:41
@gilhoffer here's an example of filters usage: http://demo.redash.io/queries/61#77
note that it applies for all visualizations/data table (see source to see how it's defined)
@gilhoffer it's a client side filter, which has the benefit of being very responsive (and easy to implement). but has the downside of being less flexible
gilhoffer
@gilhoffer
Dec 01 2014 07:20
Thanks! it's a nice trick :) any other magics which can be helpful? (e.g. any way to define multiple filters?)
Arik Fraimovich
@arikfr
Dec 01 2014 07:28
@gilhoffer yes, you can have multiple columns as filters, although sometimes it will require you to query the data differently for the data to make sense. Also there is "::multi-filter" which allows you to select multiple options.
@gilhoffer there is also a very alpha stage option to enable filters on a dashboard level, but that's done by directly updating the dashboard object in the database.
gilhoffer
@gilhoffer
Dec 01 2014 07:35
cool, thanks - I'll play with it a bit.
gilhoffer
@gilhoffer
Dec 01 2014 10:13
yep, this is becoming useful. Is there any way to hide the column that I'm using as the filter?
Arik Fraimovich
@arikfr
Dec 01 2014 12:42
@gilhoffer nope
Daniel Chalef
@danielchalef
Dec 01 2014 15:53
Hi all, I've configured the .env file with our Google Auth credentials. What are the next steps? What is the redirect URI? And how do I get the Google auth button to appear on the login page?
gilhoffer
@gilhoffer
Dec 01 2014 15:54
Just did it yesteday - the redirect URI is the server URI (HTTP and/or HTTPS) + /oauth/google_callback .
make sure to restart re:dash: sudo supervisorctl restart redash_server
and wait a few minutes for the Google changes to take effect.
Daniel Chalef
@danielchalef
Dec 01 2014 15:56
excellent. thank you!
gilhoffer
@gilhoffer
Dec 01 2014 15:56
no problem
Daniel Chalef
@danielchalef
Dec 01 2014 15:59
odd - for some reason the Google thinks that the redirect_uri in the callback is "http" and not "https" as I've defined in Google OAuth web application setup. I have setup nginx to force requests over ssl.
I've added the "http" redirect_uri to the list but find it odd that I have to.
Thanks again @gilhoffer. it is working well for me, despite the protocol hiccup.
gilhoffer
@gilhoffer
Dec 01 2014 16:01
no problem, I'm just a user, the kudos goes to @arikfr :)
Arik Fraimovich
@arikfr
Dec 01 2014 16:01
@danielchalef maybe you first configured it with http? it takes time for Google to propagate those changes
@danielchalef it can be an issue with re:dash, I need to check the code, but maybe the callback URI it passes is the one with http? In this case, it's probably nginx settings (need to tell it to pass the actual protocol)
I can look up the necessary settings if you want
Daniel Chalef
@danielchalef
Dec 01 2014 16:09
@arikfr not critical. It's working well for me now.
Arik Fraimovich
@arikfr
Dec 01 2014 16:10
@danielchalef ok. feel free to ping me if you have questions. here or by email (arik@arikfr.com)
Daniel Chalef
@danielchalef
Dec 01 2014 16:10
thanks, @arikfr