You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/03/30 05:36:20 UTC

[GitHub] [superset] lmaloney opened a new issue #19426: "Select All" functionality needed in column select

lmaloney opened a new issue #19426:
URL: https://github.com/apache/superset/issues/19426


   ### Discussed in https://github.com/apache/superset/discussions/18247
   
   <div type='discussions-op-text'>
   
   <sup>Originally posted by **cccs-rc** February  1, 2022</sup>
   Hi all, 
   
   Having recently deployed 1.4, we've discovered that the "Select All" option (pictured below as seen in 1.3) was removed from column SelectControl in the Explore view. It appears to have been a conscious decision made during the work done for [this SelectControl refactoring PR](https://github.com/apache/superset/pull/16510/files). However, our users rely heavily on that "Select All" functionality, so we're hoping this can be brought back in some form or fashion. 
   
   <img src="https://user-images.githubusercontent.com/62034438/152042546-27a0095a-7e9e-448b-9f12-2f8e98698ac7.png" width="300">
   
   Without a "Select All" functionality, users are forced to manually select all the fields they wish to include in a chart. This doesn't scale well when dealing with datasets that have 100+ columns. Our users often want to view such data sets in table charts. While they may ultimately decide to pare the number of fields down to those that are most relevant to their use cases, when users are initially developing charts, it can be critical for them to be able to easily view all the fields/data available in order to identify which fields are most relevant. 
   
   Our users rely on this functionality so heavily that we've already jammed it back into our fork, so we've seen that things can get a little weird in the UI with the new functionality _and_ a Select All option (e.g., when selected fields are moved to the top of the column list, where should the "Select All" button go?). We're hoping we can come up with a design that will allow us to keep the "Select All" functionality while maintaining good UX. 
   
   We're happy to do the work and put in a PR if we can get some insight into what criteria the design should meet. 
   
   Any thoughts/insight would be much appreciated! 
   
   Thanks! 
   </div>


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] villebro commented on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
villebro commented on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1082989215


   Thanks for opening the issue @lmaloney. This has been raised by many people since the option was removed. The main motivation for removal is that selecting all columns is a fairly uncommon use case when creating charts - the majority of charts would not easily handle grouping by 100+ columns, both from a visualization perspective, but also from a query performance perspective. However, I understand the use case e.g. in the table chart when using "raw records" mode. Out of curiosity, are you looking to use it exclusively in "raw records" mode in the table chart, or in other charts, too?


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] lmaloney edited a comment on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
lmaloney edited a comment on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1083155546


   Ah, I think there is a disconnect here....
   
   My use case, as well as "CCC-RC" (I suspect) use case is the data table chart.
   
   I don't really use the graphing functionality all that much of the charts... I do.. but, 90% of the charts I produce are data tables.  Either raw data, OR summaries of data. 
   
   Unfortunately most of the data tables just have LOTS of columns.
   
   The data is pre-processed, and cached. (the underlying data table is actually a _view_, with **pre-match** results stored in a lookup table that just used the IDs).
   
   So querying the results (even in the tens of thousands ) takes sub-second time.  Of course the presentation within SuperSet is limited to a few thousand at a time.
   
   So, yes, it's primarily "raw" and it's the data table.
   
   I've been using Superset for my application for the past six months, and I love it so much.  I have not experienced any bugs or problems, and I'm looking forward to getting some spare time to contribute to the project.
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] lmaloney edited a comment on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
lmaloney edited a comment on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1083155546


   Ah, I _think_ there is a disconnect here....
   
   My use case, as well as "CCC-RC" (I suspect) use case is  indeed the **_data table chart._**
   
   I don't really use the graphing functionality all that much of the charts... I do.. but, 90% of the charts I produce are data tables.  Either raw data, OR summaries of data. 
   
   Unfortunately most of the data tables just have LOTS of columns.
   
   The data is pre-processed, and cached. (the underlying data table is actually a _view_, with **pre-match** results stored in a lookup table that just uses the IDs).
   
   So querying the results (even in the tens of thousands ) takes sub-second time.  Of course the presentation within SuperSet is limited to a few thousand at a time.
   
   So, yes, it's primarily "raw" and it's the data table.
   
   I've been using Superset for my application for the past six months, and I love it so much.  I have not experienced any bugs or problems, and I'm looking forward to getting some spare time to contribute to the project.
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] lmaloney commented on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
lmaloney commented on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1083155546


   Ah, I think there is a disconnect here....
   
   My use case, as well as "CCC-RC" (I suspect) use case is the data table chart.
   
   I don't really use the graphing functionality all that much of the charts... I do.. but, 90% of the charts I produce are data tables.  Either raw data, OR summaries of data. 
   
   Unfortunately most of the data tables just have LOTS of columns.
   
   The data is pre-processed, and cached. (the underlying data table is actually a few, with pre-match results stored in a lookup table that just used the IDs).
   
   So querying the results (even in the tens of thousands ) takes sub-second time.  Of course the presentation within SuperSet is limited to a few thousand at a time.
   
   So, yes, it's primarily "raw" and it's the data table.
   
   I've been using Superset for my application for the past six months, and I love it so much.  I have not experienced any bugs or problems, and I'm looking forward to getting some spare time to contribute to the project.
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] lmaloney edited a comment on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
lmaloney edited a comment on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1083155546


   Ah, I think there is a disconnect here....
   
   My use case, as well as "CCC-RC" (I suspect) use case is the data table chart.
   
   I don't really use the graphing functionality all that much of the charts... I do.. but, 90% of the charts I produce are data tables.  Either raw data, OR summaries of data. 
   
   Unfortunately most of the data tables just have LOTS of columns.
   
   The data is pre-processed, and cached. (the underlying data table is actually a _view_, with **pre-match** results stored in a lookup table that just uses the IDs).
   
   So querying the results (even in the tens of thousands ) takes sub-second time.  Of course the presentation within SuperSet is limited to a few thousand at a time.
   
   So, yes, it's primarily "raw" and it's the data table.
   
   I've been using Superset for my application for the past six months, and I love it so much.  I have not experienced any bugs or problems, and I'm looking forward to getting some spare time to contribute to the project.
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] lmaloney edited a comment on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
lmaloney edited a comment on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1083155546


   Ah, I _think_ there is a disconnect here....
   
   My use case, as well as "CCC-RC" (I suspect) use case is  indeed the **_data table chart._**
   
   I don't really use the graphing functionality all that much of the charts... I do.. but, 90% of the charts I produce are data tables.  Either raw data, OR summaries of data. 
   
   Unfortunately most of the data tables just have LOTS of columns.
   
   The data is pre-processed, and cached. (the underlying data table is actually a _view_, with **pre-match** results stored in a lookup table that just uses the IDs).
   
   So querying the results (even in the tens of thousands ) takes sub-second time.  Of course the presentation within SuperSet is limited to a few thousand at a time.  Ergo, performance has not been an issue at all.
   
   So, yes, it's primarily "raw" and it's the data table.
   
   To help persuade justifying re-instatement of this feature, I would point out the obvious... that if many people have raised this issue... then it is indeed used quite a bit! :)
   
   Finally, I want to state that I've been using Superset for my application for the past six months, and I love it so much.  I have not experienced any bugs or problems, and I'm looking forward to getting some spare time to contribute to the project.
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] lmaloney edited a comment on issue #19426: "Select All" functionality needed in column select

Posted by GitBox <gi...@apache.org>.
lmaloney edited a comment on issue #19426:
URL: https://github.com/apache/superset/issues/19426#issuecomment-1083155546


   Ah, I _think_ there is a disconnect here....
   
   My use case, as well as "CCC-RC" (I suspect) use case is  indeed the **_data table chart._**
   
   I don't really use the graphing functionality all that much of the charts... I do.. but, 90% of the charts I produce are data tables.  Either raw data, OR summaries of data. 
   
   Unfortunately most of the data tables just have LOTS of columns.
   
   The data is pre-processed, and cached. (the underlying data table is actually a _view_, with **pre-match** results stored in a lookup table that just uses the IDs).
   
   So querying the results (even in the tens of thousands ) takes sub-second time.  Of course the presentation within SuperSet is limited to a few thousand at a time.
   
   So, yes, it's primarily "raw" and it's the data table.
   
   To help persuade justifying re-instatement of this feature, I would point out the obvious... that if many people have raised this issue... then it is indeed used quite a bit! :)
   
   Finally, I want to state that I've been using Superset for my application for the past six months, and I love it so much.  I have not experienced any bugs or problems, and I'm looking forward to getting some spare time to contribute to the project.
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org