[ 
https://issues.apache.org/jira/browse/SAMZA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Chen updated SAMZA-277:
-----------------------------

    Attachment: SAMZA-277.2.patch

b.q. I am leaning toward (2), mostly because we have very long prefix names for 
some configs, and it's impossible to remember them. For example, if I want to 
look up the broker list for a Kafka system, I'd have to type 
systems.kafka.producer before I would get close to what I want, vs. just typing 
"broker".

Sounds good to me. That is actually simpler to implement. :)

I am uploading a new patch that only adds a search box to the config table that 
searches both keys and values in the table. Typing '/' will automatically focus 
on the search box. Also, typing ESC will un-focus from the search box.

> Config table on ApplicationMaster web interface should collapse and expand
> --------------------------------------------------------------------------
>
>                 Key: SAMZA-277
>                 URL: https://issues.apache.org/jira/browse/SAMZA-277
>             Project: Samza
>          Issue Type: Wish
>    Affects Versions: 0.8.0
>            Reporter: Jakob Homan
>            Assignee: David Chen
>             Fix For: 0.8.0
>
>         Attachments: SAMZA-277.1.patch, SAMZA-277.2.patch, Screen Shot 
> 2014-07-07 at 1.10.24 AM.png
>
>
> Our configs are hierarchical (x.y.z) and can be quite numerous.  We can now 
> sort the table, but it would be great to be able to collapse and expand bits 
> of the table based on the hierarchy.
> * A complete collapse table would show just the {{x}} sections.
> * Expanding one level down would show {{x.y}} values, both those to be 
> further expanded and those that are fully expanded.  
> * etc. for each level.
> This would make it easy to quickly jump from one bit of config to another.  I 
> poked around, looking for a jquery library, but didn't immediately see a good 
> match.  Most of the hierarchical tree libraries are for file systems, which 
> doesn't really fit here.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to