Alexander Polyankin

### metrics-editing.cy.spec.ts location: - [x] homepage - [ ] auto pinning data source: - [x] table - [x] question single/multi stage - [x] model single/multi stage - [x] metric single/multi...

`should allow drills on FK columns from dashboards` E2E test fails because there is a mismatch between metadata in `/api/table/card__:id/query_metadata` and `/api/card/:id`. [Run link](https://app.replay.io/team/dzoyNTM4ZjRmOC05YmFlLTRiYjYtYjljYi1jOGYzOWUyMjRhZWY=/runs?testRunId=626f055a-eefb-4146-96b5-140dc39cf2ff&testId=dHJ0OjliZDEzY2U0NjhiZjU4ZTlkNDkyYmZjMWFiYWE1Y2JkMTBjMDhhN2U%3D) Actual: - `semantic_type` of the overriden...

Disable metric joins & revert join-related changes

2

Fixes https://github.com/metabase/metabase/issues/42463 Related https://github.com/metabase/metabase/issues/42278 - Removes joins for the first stage of metric-based queries - Removes metrics from the join source picker - Reverts step title changes

Remove suggested join conditions, automatically added aggregation clauses for metrics

Depends on https://github.com/metabase/metabase/issues/42462 Modify `availableMetrics` - If `source-card` is a metric, return only it - If `source-table` is a table, return all metrics compatible with this table (metrics v1 behavior)....

The test `metabase.driver.druid.query-processor-test/metrics-inside-aggregation-clauses-test` is failing because the (old) druid driver doesn't support nested queries. This test is now commented out. There are several ways to "fix" this: 1. Change QP...

Support v1 behavior: - Return compatible metrics in /api/table/:id/query_metadata as before - Allow referencing compatible metrics in queries without joins (previous behavior)

1. Cannot join to a metric - always 2. If data source is a metric, then disallow joins completely on the first stage of the query