Re: Data Provenance is not available
Pablo, Also, keep in mind that policies are inherited by child components (processors, process groups, etc), so you can enable viewing of Data Provenance for the whole flow for a given user by adding the user to the root group's "view the data" policy. Unless that policy is explicitly overridden for a child component, that user will be able to see data provenance for all components. On Mon, Nov 21, 2016 at 6:07 PM Jeffwrote: > Hi Pablo > > From the global policies menu, you can add the users that need to able to > query Data Provenance to the "query provenance" policy. > > For any component, such as the root group, or a particular processor, > you'll also want to add the user to "view the data" policies for the > respective components. > > On Mon, Nov 21, 2016 at 5:52 PM Pablo Lopez > wrote: > > Ok. Thanks for that. > Would you know how can I enable this again? > > Pablo. > > On Tue, Nov 22, 2016 at 6:44 AM, Andrew Grande wrote: > > Yes. > > It's a combination of a generic view data permission in the global menu > and specific access in the processing group. > > Andrew > > On Mon, Nov 21, 2016, 12:28 PM Pablo Lopez > wrote: > > Hi, > > Any ideas as of why Data Provenance option is grayed out (not available) > and none of the processors show the option in the context menu? Is this > something to do with security? > > Thanks, > Pablo. > > > > > -- > Pablo Lopez. > Integration Architect > Integrado Pty Ltd > M: 044 84 52 479 > pablo.lo...@integrado.com.au > >
Re: Data Provenance is not available
Hi Pablo >From the global policies menu, you can add the users that need to able to query Data Provenance to the "query provenance" policy. For any component, such as the root group, or a particular processor, you'll also want to add the user to "view the data" policies for the respective components. On Mon, Nov 21, 2016 at 5:52 PM Pablo Lopezwrote: > Ok. Thanks for that. > Would you know how can I enable this again? > > Pablo. > > On Tue, Nov 22, 2016 at 6:44 AM, Andrew Grande wrote: > > Yes. > > It's a combination of a generic view data permission in the global menu > and specific access in the processing group. > > Andrew > > On Mon, Nov 21, 2016, 12:28 PM Pablo Lopez > wrote: > > Hi, > > Any ideas as of why Data Provenance option is grayed out (not available) > and none of the processors show the option in the context menu? Is this > something to do with security? > > Thanks, > Pablo. > > > > > -- > Pablo Lopez. > Integration Architect > Integrado Pty Ltd > M: 044 84 52 479 > pablo.lo...@integrado.com.au >
Re: Data Provenance is not available
Yes. It's a combination of a generic view data permission in the global menu and specific access in the processing group. Andrew On Mon, Nov 21, 2016, 12:28 PM Pablo Lopezwrote: > Hi, > > Any ideas as of why Data Provenance option is grayed out (not available) > and none of the processors show the option in the context menu? Is this > something to do with security? > > Thanks, > Pablo. >
GetDynamoDB multiple fields
Hi, I'm using the GetDynamoDB processor and it works fine. However, whenever I get a record from DynamoDB it seems that in the processor we can only retrieve one field at a time DynamoDB. The field to read is specified in attribute "Json Document attribute". This can only point to only one field. Is there a way to retrieve the value of all the fields in the record rather than only one? I can work around this by using multiple processors and each one read a different field, but I was wondering if there is a better way to do this. Thanks, Pablo.
Code index question about PutElasticSearchHttp.java#L333
Hello everybody, I have a small question concerning the putElasticSearch.java code… While reading through the code I found the following line… https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearchHttp.java#L333 Maybe it is a dumb question, but is the index in the remove (i.e. “i”) the index it was intended for (think about what happens if run on at least two items)? Thanks in advance, Regards, Andreas Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição