-
Notifications
You must be signed in to change notification settings - Fork 21
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
M21 rebase #952
M21 rebase #952
Conversation
…uded (getredash#3600) * Fix: make sure that only the top level node_modules directory is excluded * Remove old unused packing script
* Update pack * Remove node_modules before packing
* change API to /api/queries/:id/dropdowns/:dropdown_id * extract property * split to 2 different dropdown endpoints and implement the second * make access control optional for dropdowns (assuming it is verified at a different level) * add test cases for /api/queries/:id/dropdowns/:id * use new /dropdowns endpoint in frontend * require access to dropdown queries when creating or updating parent queries * rename Query resource dropdown endpoints * check access to dropdown query associations in one fugly query * move ParameterizedQuery to models folder * add dropdown association tests to query creation * move group by query ids query into models.Query * use bound parameters for groups query * format groups query * use new associatedDropdowns endpoint in dashboards * pass down parameter and let it return dropdown options. Go Levko! * change API to /api/queries/:id/dropdowns/:dropdown_id * split to 2 different dropdown endpoints and implement the second * use new /dropdowns endpoint in frontend * pass down parameter and let it return dropdown options. Go Levko! * fix bad rebase * add comment to clarify the purpose of checking the queryId
* Apply prettier to app-header.html. * Add: E2E test for query search
…ash#3626) * Fix a few more inconsistencies when loading and dumping JSON. Refs getredash#2807. Original work in: getredash#2817 These change have been added since c2429e9. * Review fixes.
) * Normalize Flask initialization API use. * Use Flask-Talisman. * Enable HSTS when HTTPS is enforced. * More details about how CSP is formatted and write CSP directives as a string. * Use CSP frame-ancestors directive and not X-Frame-Options for embedable endpoints. * Add link to flask-talisman docs. * set remember_token cookie to be HTTP-Only and Secure * Reorganize secret key configuration to be forward thinking and backward compatible.
… is enabled. (getredash#3530) * Make LDAP auth handler org scoped. * Render LDAP and remote auth login links correctly when multi org mode is enabled.
* Browser support config * Removed some offending code * Added unsupported html page and redirect for IE * Typo in regex * Made html page static * Added redirect script to multi_org * Moved static html page to client/app
* Add phoenix query runner. * Improved error handling.
…redash#3613) * check that e-mail server is configured before marking the email address as not verified and sending out a verification e-mail * use helper method in `invite_user` * move email_server_configured helper to settings * add test to verify that email addresses arent marked as unverified if there's no e-mail server to verify them * simplify a couple of tests with patch * combine conditions into single variable * Booleans, gotta love 'em
…dash#3592) * allowing to specify a custom work group for AWS Athena queries * Fixing title + adding correct position in the UI
…sh#3599) * Show accessible tables only. * Get table information from information_schema.columns. * Union old query.
* Return 400 when destination name already exists * Remove whitespace * Unicode 1 Co-Authored-By: gabrieldutra <nesk.frz@gmail.com> * Unicode 2 Co-Authored-By: gabrieldutra <nesk.frz@gmail.com>
There are 6 commits up at https://github.com/mozilla/redash/tree/emtwo/m21 :
However, the only minor issue is that when a new data source is created, it doesn't automatically populate the version toggle or doc url, they remain empty. So by default these features would not be on. I am just proposing a way in that commit to make them default on. |
* Process extra column metadata for a few sql-based data sources. * Add Table and Column metadata tables. * Periodically update table and column schema tables in a celery task. * Fetching schema returns data from table and column metadata tables. * Add tests for backend changes. * Front-end shows extra table metadata and uses new schema response. * Delete datasource schema data when deleting a data source. * Process and store data source schema when a data source is first created or after a migration. * Tables should have a unique name per datasource. * Addressing review comments. * Update migration file for mixins. * Appease PEP8 * Upgrade migration file for rebase. * Cascade delete. * Adding org_id * Remove redundant column and table prefixes. * Non-existing tables and columns should be filtered out on the server side not client side. * Fetching table samples should be optional and should happen in a separate task per table. * Allow users to force a schema refresh. * Use updated_at to help prune old schema metadata periodically. * Using settings.SCHEMAS_REFRESH_QUEUE * fix for getredash#2426 test * more stable test_interactive_new * Closes #927, #928: Schema refresh improvements. * Closes #934, #935: Remove type from schema browser and don't show empty example column in schema drawer (#936) * Speed up schema fetch requests with fewer postgres queries. * Add column metadata to Athena glue processing. * Fix bug assuming 'metadata' exists for every table. * Closes #939: Persisted, existing table metadata should be updated. * Sample processing should be rate-limited. * Add cli command for refreshing data samples. * Schema refreshes should not overwrite column 'example' field. * refresh_samples() should filter tables_to_sample on the datasource's id being sampled * Correctly wrap long text in schema drawer. Co-authored-by: Alison <github@bankofknowledge.net>
I've merged those commits into the individual feature commits.
Hm, that'd be odd, I'll double check this..
Ok, let's go with the patch and see if this makes sense. Can you follow-up with this upstream after the deploy? |
Yes thank you I wanted to also ask if you could do that.
Well this patch is a proposal so it would need more changes to work for all data source. I've only done it for postgres as an example. It would also need a change in the I can file an issue upstream though I think this might be intended behaviour. Given the fact that this is a small issue with intended behaviour and requires changes to |
Makes sense to me, I'll remove
Sure no problem.
Okay, that works for me, so I'm removing e999042b1c5a1075bb8143dcebc3e84f292316f6 again? |
Yes please. Sorry for the confusion |
All good, just wanted to be clear. 👍 |
This has been pushed to release. |
Closing since this has been merged and released. |
Applied commits
Dropped commmits
Dropped commits WITH TODOs
Collapsed commits (of the applied above)