kz930 opened a new issue, #7324: URL: https://github.com/apache/texera/issues/7324
### What happened? `attributeTypeRules` is how an operator states which column types a picker accepts, and upstream already uses it wherever a chart consumes a column as a quantity — Range Slider constrains its `Y-axis`, Radar Chart its `Value Columns`. Two pickers consume their column the same way and declare no rule at all, so the form offers every column and accepts a string one. Wind Rose's `Radial Values (r)` is the length of each wedge. Given a string column, plotly switches the radial axis from a linear one to a categorical one: the wedges are drawn at ordinal positions rather than magnitudes, so the chart renders and looks finished while its lengths carry no meaning. Rendering the same three-row frame twice in a browser, `radialaxis.type` is `linear` with range 0 to 4.2 for the numeric column and `category` with range −0.11 to 2.11 for the string one — and this holds even when every value is a number written as text, so no user data recovers the correct chart. Bubble Chart's `Z-Column` is the bubble size, which plotly express divides by a scale factor, so a string column aborts the run with `TypeError: unsupported operand type(s) for /: 'str' and 'int'`. A numeric-looking string fails identically. Expected: both pickers offer only integer, long and double, the way Range Slider's `Y-axis` does. ### How to reproduce? Drop either operator after a source that has a string column. For Wind Rose select it as `Radial Values (r)` with any column as the angle — with wedge values 1, 4 and 2 the numeric column draws them in proportion and the string column draws the third wedge largest, with no error. For Bubble Chart select it as `Z-Column` — the run aborts with the TypeError above. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main) -- 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]
