[
https://issues.apache.org/jira/browse/SOLR-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013042#comment-18013042
]
Christos Malliaridis commented on SOLR-17846:
---------------------------------------------
{quote}I think the only tough one is the displaying all the field types, how to
handle all the columns!{quote}
Yes, I don't like the fact that I use data tables / lists everywhere, but most
of the times it is the easiest way to show the data we have. The problem of too
many columns can be solved by providing a component similar to the [data table
from react MUI|https://mui.com/material-ui/react-table/#data-table], where the
user can hide and display columns, as well as sort by them.
I plan to implement a similar component for all the tables / lists we have in
SOLR-17660.
{quote}Configsets is super powerful capablity, and it's not addressed in the
legagcy UI...{quote}
If you know of any other features that may be missing in the legacy UI, we can
try to address them in the new UI. :)
> Introduce Configset Management in Admin UI
> ------------------------------------------
>
> Key: SOLR-17846
> URL: https://issues.apache.org/jira/browse/SOLR-17846
> Project: Solr
> Issue Type: New Feature
> Components: Admin UI
> Reporter: Christos Malliaridis
> Priority: Major
> Labels: new-ui, ui
>
> One of the key resources of Solr are configsets. User should be capable of
> managing configsets freely with all their features.
> h2. Scope
> The scope of this ticket is the entire
> [Configsets|https://www.figma.com/design/VdbEfcWQ8mirFNquBzbPk2/Apache-Solr-Admin-UI-v2-Concept?node-id=14-3248&t=3d0o3InCzstyUJ40-1]
> section. Devs should work on sub-tasks so that PRs are kept small enough and
> reviewable.
> h2. Acceptance Criteria
> This ticket can be closed once all sections of the "Configsets" are defined,
> designed and implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
