dosubot[bot] commented on issue #35499: URL: https://github.com/apache/superset/issues/35499#issuecomment-3367246397
<!-- Answer --> This looks like a real bug: in 6.0.0rc2, deck.gl scatterplots are being auto-migrated to "fixed color" (all points the same color), but the legend still shows the old categorical palette, which is inconsistent. This issue isn't tracked in the docs or issue tracker, but similar problems have been reported in earlier versions and were fixed by syncing color and legend logic in the chart code ([example](https://github.com/apache/superset/issues/32841), [fix PR](https://github.com/apache/superset/pull/33748)). In your case, it seems the migration or upgrade logic is forcing "fixed color" without updating the legend config, leading to the mismatch. There's no official workaround documented, but you can manually switch the color scheme type back to "categorical" in the chart controlsāthis should restore the expected color mapping and legend. If you see the legend disappear when you set "fixed color," that's expected behavior. If you continue to see issues, double-check your chart's control panel settings, as legend visibility and color assignment depend on those ([discussion](https://github.com/apache/superset/issues/34822), [discussion](https://github.com/apache/superset/discussions/32892)). If you need to ensure categorical colors and legends work for multi-layer deck.gl charts, the recommended approach is to use the CategoricalDeckGLContainer component, which manages categories, color assignment, and legend rendering ([guide](https://github.com/apache/superset/discussions/32892)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1d29e934-a6aa-492f-8e22-1b11b5509422?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35499) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
