[jira] [Commented] (NIFI-404) Update developer guide to explain the NAR's Native Library isolation in addition to ClassLoader isolation
[
https://issues.apache.org/jira/browse/NIFI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661829#comment-14661829
]
Brandon DeVries commented on NIFI-404:
--
[~markap14], where in the NAR is the "native" directory supposed to go? I put
it at "foo.nar/META-INF/bundled-dependencies/native", then
"foo.nar/META-INF/native", then just "foo.nar/native"... nothing (except a
java.lang.UnsatisfiedLinkError"). If I take that same native directory and
drop in in the lib directory, and add
{code}
java.arg.11=-Djava.library.path=./lib/native
{code}
as before, that works. So... thoughts?
> Update developer guide to explain the NAR's Native Library isolation in
> addition to ClassLoader isolation
> -
>
> Key: NIFI-404
> URL: https://issues.apache.org/jira/browse/NIFI-404
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
>Reporter: Mark Payne
>
> Need to explain that native libraries existing in the native/ directory are
> isolated to that NAR and explain how to add native libraries to that
> directory via Maven.
> Our documentation for how the NAR Classloader works and its purpose does not
> clearly call out the limitations. For example, if one wants to use some
> version of Jetty or logback can they? How so? We need to show a clear diagram
> of how the NAR classloading works and so on so folks can more readily reason
> over it.
> NAR stuff is very powerful and helpful but today it is a bit too magical
> without this complete documentation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-404) Update developer guide to explain the NAR's Native Library isolation in addition to ClassLoader isolation
[ https://issues.apache.org/jira/browse/NIFI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661997#comment-14661997 ] Brandon DeVries commented on NIFI-404: -- So, this is an id10t error if you put the native dir at "foo.nar/META-INF/bundled-dependencies/native" of the NAR that actually needs it, it works just fine. Carry on. > Update developer guide to explain the NAR's Native Library isolation in > addition to ClassLoader isolation > - > > Key: NIFI-404 > URL: https://issues.apache.org/jira/browse/NIFI-404 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Mark Payne > > Need to explain that native libraries existing in the native/ directory are > isolated to that NAR and explain how to add native libraries to that > directory via Maven. > Our documentation for how the NAR Classloader works and its purpose does not > clearly call out the limitations. For example, if one wants to use some > version of Jetty or logback can they? How so? We need to show a clear diagram > of how the NAR classloading works and so on so folks can more readily reason > over it. > NAR stuff is very powerful and helpful but today it is a bit too magical > without this complete documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-826) Export templates in a deterministic way
Matt Gilman created NIFI-826: Summary: Export templates in a deterministic way Key: NIFI-826 URL: https://issues.apache.org/jira/browse/NIFI-826 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Matt Gilman Fix For: 0.3.0 Templates should be exported in a deterministic way so that they can be compared or diff'ed with another. Items to consider... - The ordering of components - The id's used to identify the components - Consider excluding irrelevant items. When components are imported some settings are ignored (run state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-827) Add system property indicating Headless Mode
Matt Gilman created NIFI-827:
Summary: Add system property indicating Headless Mode
Key: NIFI-827
URL: https://issues.apache.org/jira/browse/NIFI-827
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Matt Gilman
Priority: Trivial
Fix For: 0.3.0
Apache NiFi is a headless Java application. As such we should enable headless
mode by setting
{code}-Djava.awt.headless=true{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (NIFI-828) Update default filter in new Processor Dialog
Matt Gilman created NIFI-828: Summary: Update default filter in new Processor Dialog Key: NIFI-828 URL: https://issues.apache.org/jira/browse/NIFI-828 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Trivial Fix For: 0.3.0 Update the default filter in the new processor dialog to use 'by tag' instead of 'by name'. A user will likely want to search for items using terms tagged on the processor rather than the formal processor name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-829) When using InvokeHTTP, the provenance lineage indicates that it has a cycle and produces an error instead of showing the lineage
Mark Payne created NIFI-829: --- Summary: When using InvokeHTTP, the provenance lineage indicates that it has a cycle and produces an error instead of showing the lineage Key: NIFI-829 URL: https://issues.apache.org/jira/browse/NIFI-829 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Mark Payne Fix For: 0.3.0 InvokeHTTP emits CLONE and RECEIVE provenance events but would expect a CONTENT_MODIFIED. This is a good example, like FetchHDFS, where we really need a FETCH provenance event, because the content is being modified by replacing it with the result of a network request. In the meantime, though, the RECEIVE I think should instead be a CONTENT_MODIFIED. Also, I think that a FORK may be more appropriate than a CLONE, since the content of the newly created FlowFile is also changed in the processor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-830) For GET requests, InvokeHTTP should set the filename of the 'Response' FlowFile based on the URL
Mark Payne created NIFI-830:
---
Summary: For GET requests, InvokeHTTP should set the filename of
the 'Response' FlowFile based on the URL
Key: NIFI-830
URL: https://issues.apache.org/jira/browse/NIFI-830
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: Mark Payne
Priority: Minor
Fix For: 1.0.0
When using InvokeHTTP to fetch the content of a particular URL, I expected that
the filename of the 'Response' FlowFile would be set to the filename pulled.
I.e., if I pulled http://www.somesite.com/images/1.png, I would have expected
the 'Response' FlowFile to have a filename of "1.png" but instead it had the
same filename as the incoming FlowFile.
I don't think this is something that we can change until version 1.0.0 because
it could potentially break backward compatibility of flows by changing the
filename unexpectedly. In the meantime, I have added an UpdateAttribute to set
the filename to ${url:substringAfterLast('/'):substringBefore('?')}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-821) Support Merging of Avro
[ https://issues.apache.org/jira/browse/NIFI-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662724#comment-14662724 ] Joseph Witt commented on NIFI-821: -- [~markap14] please do try to take a look and help review this one. MergeContent is a magical beast > Support Merging of Avro > --- > > Key: NIFI-821 > URL: https://issues.apache.org/jira/browse/NIFI-821 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.4.0 > > Attachments: NIFI-821.patch > > > We should support the ability to merge Avro files of the same schema, similar > to how MergeContent works. > Avro tools provides a command line tool for doing this which can be found > here: > https://github.com/apache/avro/blob/trunk/lang/java/tools/src/main/java/org/apache/avro/tool/ConcatTool.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-821) Support Merging of Avro
[ https://issues.apache.org/jira/browse/NIFI-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-821: - Fix Version/s: (was: 0.4.0) 0.3.0 > Support Merging of Avro > --- > > Key: NIFI-821 > URL: https://issues.apache.org/jira/browse/NIFI-821 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.3.0 > > Attachments: NIFI-821.patch > > > We should support the ability to merge Avro files of the same schema, similar > to how MergeContent works. > Avro tools provides a command line tool for doing this which can be found > here: > https://github.com/apache/avro/blob/trunk/lang/java/tools/src/main/java/org/apache/avro/tool/ConcatTool.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
