This project is mirrored from https://github.com/metabase/metabase.
Pull mirroring updated .
- Dec 10, 2024
-
-
github-automation-metabase authored
* Add new user-level setting * Add selector * Make link dismissible from the sidebar * Transfer the onboarding link to the main "gear" menu * Add E2E test to cover the link dismissal behavior * Add tests for the settings menu link * Fix tests * Provide useful comment in the e2e test * Provide contextual explanations to translators Co-authored-by:
Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>
-
github-automation-metabase authored
* Avoid logging trace * Demote log to warning Co-authored-by:
lbrdnk <lbrdnk@users.noreply.github.com>
-
github-automation-metabase authored
Add binning to display name similarly as done with bucketing. --------- Co-authored-by:
lbrdnk <lbrdnk@users.noreply.github.com> Co-authored-by:
metamben <103100869+metamben@users.noreply.github.com>
-
Jeff Bruemmer authored
-
github-automation-metabase authored
Co-authored-by:
Nathan Voxland <nathan@metabase.com>
-
github-automation-metabase authored
* We need to look at the context field to categorize public views * pull poll-unil into util ns * fix comment typo * add test * update docstring * remove true? call, it will return `true` on pass * improve poll-until Co-authored-by:
bryan <bryan.maass@gmail.com>
-
github-automation-metabase authored
* Fix the zoom-in.timeseries drill for multi-stage queries If no dimensions are provided to the zoom-in.timeseries drill, then attempt to find the matching dimension from the FE-provided row data instead, if present. Related to https://github.com/metabase/metabase/issues/46932 * Only return zoom-in.timeseries drills for clicks on aggregated columns Co-authored-by:
appleby <86076+appleby@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
- Dec 09, 2024
-
-
github-automation-metabase authored
The underlying issue is that nest-query/nest-expression included temporal units when copying over joined fields into the nested query. This caused both the nested query and the parent query to include the "extract the unit from the date" code. In cases where the extraction didn't change the type, this duplication wasn't a big deal. However, for temporal units like hour-of-day, the first extraction changed the type of the field from date to string, and then the second extraction broke. This change ensures that the inner query doesn't try to extract temporal units, which should avoid the duplicate extractions. Co-authored-by:
William <william@metabase.com>
-
github-automation-metabase authored
* feat: Introduce describe-indexes Fixes: #49981 Introduce a faster sync with describe-indexes that follows describe-fields and describe-fks to allow for a database wide sync step rather per table describe-table-indexes. Implement for psotgres * Fix formatting * Add tests * Update src/metabase/driver.clj * Update src/metabase/driver.clj * Address PR review * Fix null schema check --------- Co-authored-by:
Case Nelson <case@metabase.com> Co-authored-by:
metamben <103100869+metamben@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Jeff Bruemmer <jeff.bruemmer@gmail.com>
-
- Dec 06, 2024
-
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
- Dec 05, 2024
-
-
github-automation-metabase authored
* fix the script, and add the new edn * make the migrations run in the proper order * it works (needs cleanup) * remove broken binning - These bins rely on fingerprinting for the custom Age column - The fingerprinting for that custom column are not properly exported in serialization, hence do not get loaded into metabase, causing binning by Age to fail. * cleanup / linting * cleanup * update migration test ids to test * realign test name to check for to see if sample content was created * remove Product collection + move Examples into root * update collection_ids for the content too * remove click behavior for 'Revenue goal for this quarter' * Apply suggestions from code review * for the sample collection is_sample should be true * Drop CreateInternalUserNoOp * typo * update migration comments * 2 small fixes * fix data perms for example coll * add a comment so we don't have 2 blank lines in a row --------- Co-authored-by:
bryan <bryan.maass@gmail.com> Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
William <william@metabase.com>
-
Jeff Bruemmer authored
-
github-automation-metabase authored
Co-authored-by:
Oleksandr Yakushev <alex@bytopia.org>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Noah Moss <32746338+noahmoss@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
- Dec 04, 2024
-
-
github-automation-metabase authored
Co-authored-by:
Ngoc Khuat <qn.khuat@gmail.com> Co-authored-by:
Phoomparin Mano <poom@metabase.com>
-
github-automation-metabase authored
Fixes: #50771 The new sync process failed to qualify enums outside public and therefore failed to properly type them in database_type. This could either result in matching the wrong type if there was a conflict or not being typed as an enum. Co-authored-by:
Case Nelson <case@metabase.com>
-
github-automation-metabase authored
Co-authored-by:
metamben <103100869+metamben@users.noreply.github.com>
-
github-automation-metabase authored
* Add trial banner * Use the semantic "warning" color for background * Simplify the "reappearance" logic * Refine the banner logic - Pass the bare minimum information (expiry timestamp) to the `TrialBanner` - Take timezones into account - Introduce utilities - Add unit tests * Update the remaining tests * Clean up * Unbreak my `defsetting`
* Add comments * Defer var assignment * Fix failing tests * Adjust the types in order to match `master` * Move the logic up to the parent component * Convert the `index` component to TS * Fix typo in the JSDoc * Fix another typo * Make the return statement more readable * Remove redundant test Co-authored-by:Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>
-
github-automation-metabase authored
Applying the underlying records filter to a query with a join displays fields from the join Co-authored-by:
William <william@metabase.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Alexander Solovyov <alexander@solovyov.net>
-
github-automation-metabase authored
Co-authored-by:
Ngoc Khuat <qn.khuat@gmail.com>
-
github-automation-metabase authored
Co-authored-by:
Ngoc Khuat <qn.khuat@gmail.com>
-
- Dec 03, 2024
-
-
github-automation-metabase authored
Co-authored-by:
Noah Moss <32746338+noahmoss@users.noreply.github.com>
-
github-automation-metabase authored
Pivot Exports Can Handle `nil` in Breakout Col, and Multiple Cols of the Same Aggregation Type (#50672) (#50780) * Pivot Exports Can Handle `nil` in Breakout Col, and Multiple Cols of the Same Aggregation Type Fixes #50551 If a pivot table has several measures configured, they might both use the same kind of aggregation (eg. 'sum'). Previously, this would lead to columns with the same name preventing the pivot-measures from properly making it through the export post processing. Now, the correct aliased/deduped name is used and all columns can be properly included in the pivot export. Also fixes the case where a breakout column (pivot-row) contains `nil` values, which caused the pivot export to fail. Now, all nil values are grouped and handled appropriately. * when pivot is disabled, header should still be included * min and max don't default to 0, add a test for the aggregations Co-authored-by:
adam-james <21064735+adam-james-v@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
* match against any hexadecimal bundle name * add e2e tests skeleton * Support display-name for ISO get-day-of-week exclusion expressions (#50606) * Support display-name for ISO get-day-of-week exclusion expressions Fixes #50574 * Fix light theme embeddings has different text colors (#50678) * add cache-control tests * support local runs --------- Co-authored-by:
Phoomparin Mano <poom@metabase.com> Co-authored-by:
metamben <103100869+metamben@users.noreply.github.com> Co-authored-by:
Mahatthana (Kelvin) Nomsawadi <me@bboykelvin.dev>
-
- Nov 30, 2024
-
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
- Nov 29, 2024
-
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
This protects against us trying to read or write from an incompatible search index. In particular it prevents existing instances from being switched over to an incompatible table during an HA upgrade or downgrade. ~~It doesn't yet get rid of the needless re-initialization, but that will be a fast follow.~~ It breaks up the jobs so that we won't reindex on startup unless necessary. Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-
github-automation-metabase authored
See https://www.notion.so/metabase/Search-Index-Maintenance-14b69354c9018047b670cbba1c3be50d This ensures that when one instance starts or finishes reindexing, the other instances pick up and switch to the same tables. Note: this does not stop blowing away the currently active table on deployment yet, we need to have a notion of version for that first. Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
-