Add hidden show capability to sensitive text-area boxes
Hi, In controller-services, for ex: HiveConnectionPool there is a property called "Password". One of our clients who use nifi wish to add the capability of hidden show (input type="password"). I understand property list table is dynamically populated using jquery (please correct me if am wrong). Below is what i suggest: When we mention like below in this case for password property: public static final PropertyDescriptor DB_PASSWORD = new PropertyDescriptor.Builder().name("hive-db-password") .displayName("Password") .description("The password for the database user") .defaultValue(null) .required(false) .sensitive(true) .addValidator(StandardValidators.NON_EMPTY_VALIDATOR) .build(); i suggest to add .hiddenshow(true) (or any other name) so that frame work can add an jquery and css appropriately to build the password like hidden show nature: "***" ( we can even replace the textarea tag to input type='password> ) only for these cases. I would like to your views on this.. Thanks Ramakrishnan V
Re: Add hidden show capability to sensitive text-area boxes
Hi, NiFi never pulls sensitive valued to the UI once set, it's a one-way operation only. Today, the UI has a hint 'sensitive value is set' to indicate it's not empty. Maybe you can provide more background on what you are trying to achieve in that context? Thanks, Andrew On Sun, Feb 12, 2017, 7:43 AM Ramakrishnan Venkatachalam < ramkrish9...@gmail.com> wrote: > Hi, > > In controller-services, for ex: HiveConnectionPool there is a property > called "Password". One of our clients who use nifi wish to add the > capability of hidden show (input type="password"). I understand property > list table is dynamically populated using jquery (please correct me if am > wrong). > > Below is what i suggest: > > When we mention like below in this case for password property: > > public static final PropertyDescriptor DB_PASSWORD = new > PropertyDescriptor.Builder().name("hive-db-password") > .displayName("Password") > .description("The password for the database user") > .defaultValue(null) > .required(false) > .sensitive(true) > .addValidator(StandardValidators.NON_EMPTY_VALIDATOR) > .build(); > > i suggest to add > > .hiddenshow(true) (or any other name) > > so that frame work can add an jquery and css appropriately to build the > password like hidden show nature: "***" ( we can even replace the > textarea tag to input type='password> ) only for these cases. > > > I would like to your views on this.. > > Thanks > Ramakrishnan V >
Re: Re: Controls the order in which processors are executed
Hi my friend: Tank you ,you are right , i only want to have a sequence of actions for my components. And the components are the result of that i edit resource,so that it is not in the list. Can you give me some advices? best wishs petter wang 2017-02-13 wangj...@weiresearch.com From: Aldrin Piri Date: 2017-02-10 21:04 To: dev Subject: Re: Controls the order in which processors are executed Hi Petter, It seems the image did not make it through to the list. Could you please upload it elsewhere and then provide a link? Are you looking to have a specific sequence of actions for your components? On Fri, Feb 10, 2017 at 1:24 AM, wangj...@weiresearch.com < wangj...@weiresearch.com> wrote: > Nifi 1.1.1 > I recently created three processors, as shown below. > > I want all selected, the first implementation of the > spiderProcessor, and then the implementation of b extractTableProcessor, > the final implementation of ChineseProcessor. In short, I would like to > have a processor on the order of the implementation of the controller, you > can help me Mody, very grateful. > > *tank you for much* > *petter wang* > *2017-02-10* > >
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
+1 (non-binding) On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries wrote: > +1 binding > On Fri, Feb 10, 2017 at 6:36 PM Andre wrote: > > > +1 binding > > > > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote: > > > > > All, > > > > > > Following a solid discussion for the past few days [1] regarding the > > > establishment of Registry as a sub-project of Apache NiFi, I'd like to > > > call a formal vote to record this important community decision and > > > establish consensus. > > > > > > The scope of this project is to define APIs for interacting with > > > resources that one or more NiFi instances may be interested in, such > > > as a flow registry for versioned flows, an extension registry for > > > extensions, and possibly other configuration resources in the future. > > > In addition, this project will provide reference implementations of > > > these registries, with the goal of allowing the community to build a > > > diverse set of implementations, such as a Git provider for versioned > > > flows, or a bintray provider for an extension registry. > > > > > > I am a +1 and looking forward to the future work in this area. > > > > > > The vote will be open for 72 hours and be a majority rule vote. > > > > > > [ ] +1 Establish Registry, a subproject of Apache NiFi > > > [ ] 0 Do not care > > > [ ] -1 Do not establish Registry, a subproject of Apache NiFi > > > > > > Thanks, > > > > > > Bryan > > > > > > [1] > > http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_ > > > M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E > > > > > >