[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746575#comment-14746575 ] Mark Payne commented on NIFI-732: - Not sure. I didn't see it 100% of the time but i did see it most of the time. But when I was testing, I was bouncing back & forth between two different topics. So it's possible that one topic had a single partition while the other had multiple partitions. Since the error had to do with rebalancing, that may make sense... > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746574#comment-14746574 ] Brian Ghigiarelli commented on NIFI-732: [~markap14] [~mcgilman] how many partitions did those Kafka topics have that you were testing? For me, the timing of GetKafka working is suspiciously close to when I switched from a single partition to multiple, regardless of the number of brokers. > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746560#comment-14746560 ] Matt Gilman commented on NIFI-732: -- I was able to start and stop successfully (after modifying the batch size) as well when testing those tickets. Don't recall ever seeing that message. > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746555#comment-14746555 ] Mark Payne commented on NIFI-732: - Interesting. I was hitting this issue when testing NIFI-939 and NIFI-938. Kept getting message about not being able to rebalance... > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746551#comment-14746551 ] Brian Ghigiarelli commented on NIFI-732: [~markap14] very strange because for the past month or so, I've been flipping between GetKafka and another Kafka consumer on our fork and both have worked just fine for localhost and remote Kafka brokers. Plenty of stops and starts in that testing too. > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-959) PutSolrContentStream not handling expression correctly for Collection property
[ https://issues.apache.org/jira/browse/NIFI-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-959: - Attachment: NIFI-959.patch > PutSolrContentStream not handling expression correctly for Collection > property > --- > > Key: NIFI-959 > URL: https://issues.apache.org/jira/browse/NIFI-959 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 0.3.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.4.0 > > Attachments: NIFI-959.patch > > > The Collection property in the Solr processors supports expression language, > and the PutSolrContentStream processor is supposed to support receiving the > Collection value from the incoming FlowFiles and be able to send to different > collections from the same processor. > The processor is evaluating the wrong value when calling > context.getProperty(..).evaluateAttributeExpressions() for the Collection, > which is causing this not to work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746165#comment-14746165 ] Mark Payne commented on NIFI-732: - It turns out that I was able to duplicate this when running against a remote Kafka broker but running on localhost i could not replicate for some reason. Not sure if it's the fact that it was on localhost or if the configuration was just different, but I've definitely been able to replicate now. > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-516) MergeContent when merging 10,000s or more objects can cause too many open files
[ https://issues.apache.org/jira/browse/NIFI-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746160#comment-14746160 ] Mark Payne commented on NIFI-516: - I think a good solution to this problem would be to add a new method to ProcessSession, so that when we call session.read(FlowFile, InputStreamCallback) we have the ability to pass a third argument: session.read(FlowFile flowFile, InputStreamCallback callback, boolean allowSessionStreamManagement); The existing read method could simply call this method passing 'true' as the third argument. If true, it would behave as it does now, where the session is allows to hold the stream open for performance reasons. However, if passing false, the session should always close the InputStream before returning. Then, in MergeContent, we can just pass 'false', so that each of those sessions doesn't hold open those resources. > MergeContent when merging 10,000s or more objects can cause too many open > files > --- > > Key: NIFI-516 > URL: https://issues.apache.org/jira/browse/NIFI-516 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Joseph Witt > Fix For: 0.4.0 > > > MergeContent really is just exposing an issue where the process session keeps > file handles open longer than necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-962) Create a processor to evaluate Avro paths
Bryan Bende created NIFI-962: Summary: Create a processor to evaluate Avro paths Key: NIFI-962 URL: https://issues.apache.org/jira/browse/NIFI-962 Project: Apache NiFi Issue Type: Improvement Reporter: Bryan Bende Assignee: Bryan Bende Priority: Minor Evaluate a set of Avro paths against an incoming file, and extract the results to FlowFile attributes, or to the content of the FlowFile, similar to EvaluateJsonPath. This would allow downstream processors to easily make decisions based on values in an Avro record, such as RouteOnAttribute. This would be particularly useful to use in conjunction with SplitAvro (NIFI-919) to make routing decisions on bare avro records. Flume has a similar concept in Morphlines that may be useful to look at: https://github.com/cloudera/cdk/blob/master/cdk-morphlines/cdk-morphlines-avro/src/main/java/com/cloudera/cdk/morphline/avro/ExtractAvroPathsBuilder.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages
[ https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-732: Assignee: Joseph Percivall (was: Mark Payne) > GetKafka if stopped then started doesn't resume pulling messages > > > Key: NIFI-732 > URL: https://issues.apache.org/jira/browse/NIFI-732 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: linux >Reporter: Joseph Witt >Assignee: Joseph Percivall > Fix For: 0.4.0 > > > A nifi user reported that they had to restart nifi to get the GetKafka > processor to resume pulling data once they had stopped the processor. Upon > restarting it showed that it was started but did not resume pulling data. > Need to attempt to reproduce and resolve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-883) HandleHttpRequest starts a web server in the OnScheduled method but should start it in onTrigger
[ https://issues.apache.org/jira/browse/NIFI-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-883: Assignee: Joseph Percivall > HandleHttpRequest starts a web server in the OnScheduled method but should > start it in onTrigger > > > Key: NIFI-883 > URL: https://issues.apache.org/jira/browse/NIFI-883 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Mark Payne >Assignee: Joseph Percivall > Labels: beginner, newbie > Fix For: 0.4.0 > > > When HandleHttpRequest is scheduled, it creates an embedded jetty web server > and starts it. Unfortunately, if this is run in a clustered environment and > configured to run on Primary Node Only, all nodes still start the web server. > This is very confusing if setting the Hostname property, as other nodes will > complain. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-631) Create ListFile and FetchFile processors
[ https://issues.apache.org/jira/browse/NIFI-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746088#comment-14746088 ] Mark Payne commented on NIFI-631: - [~jskora] - just wanted to touch base with you on this. Is this something you're still actively working? > Create ListFile and FetchFile processors > > > Key: NIFI-631 > URL: https://issues.apache.org/jira/browse/NIFI-631 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Payne > > This pair of Processors will provide several benefits over the existing > GetFile processor: > 1. Currently, GetFile will continually pull the same files if the "Keep > Source File" property is set to true. There is no way to pull the file and > leave it in the directory without continually pulling the same file. We could > implement state here, but it would either be a huge amount of state to > remember everything pulled or it would have to always pull the oldest file > first so that we can maintain just the Last Modified Date of the last file > pulled plus all files with the same Last Modified Date that have already been > pulled. > 2. If pulling from a network attached storage such as NFS, this would allow a > single processor to run ListFiles and then distribute those FlowFiles to the > cluster so that the cluster can share the work of pulling the data. > 3. There are use cases when we may want to pull a specific file (for example, > in conjunction with ProcessHttpRequest/ProcessHttpResponse) rather than just > pull all files in a directory. GetFile does not support this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-932) Allow ExecuteSQL to run periodically without any input FlowFile
[ https://issues.apache.org/jira/browse/NIFI-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende reassigned NIFI-932: Assignee: Bryan Bende > Allow ExecuteSQL to run periodically without any input FlowFile > --- > > Key: NIFI-932 > URL: https://issues.apache.org/jira/browse/NIFI-932 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Payne >Assignee: Bryan Bende > Fix For: 0.4.0 > > > Currently, ExecuteSQL will return immediately if run without a FlowFile. > Instead, it should be able to be configured to run (say once per hour) > without any input data. > The framework as-is does not provide this information, so the fact of whether > or not incoming connections exist would have to be provided by the > ProcessContext object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-960) Hashes, keys and sigs must be downloaded from the ASF mirror source
[ https://issues.apache.org/jira/browse/NIFI-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt reassigned NIFI-960: Assignee: Joseph Witt > Hashes, keys and sigs must be downloaded from the ASF mirror source > --- > > Key: NIFI-960 > URL: https://issues.apache.org/jira/browse/NIFI-960 > Project: Apache NiFi > Issue Type: Bug >Reporter: Sebb >Assignee: Joseph Witt > > The download page links to KEYS, hashes and sigs, which is good. > However, it links to the release area in SVN, which is the wrong place. > They should be downloaded from the ASF mirror source which is > http://www.apache.org/dist/nifi > The www.apache.org systems are set up for higher traffic levels and are > mirrored in EU and US. > The SVN dist system is not intended for downloading files by 3rd parties - it > is the staging area from which the main ASF hosts are populated. > Please update the download page to correct the links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-961) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/NIFI-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt reassigned NIFI-961: Assignee: Joseph Witt > Please delete old releases from mirroring system > > > Key: NIFI-961 > URL: https://issues.apache.org/jira/browse/NIFI-961 > Project: Apache NiFi > Issue Type: Bug >Reporter: Sebb >Assignee: Joseph Witt > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? i.e. all except 0.2.1 > The earlier releases can still be mentioned on the download page, but the > links should point to the archive server, i.e. > http://archive.apache.org/dist/nifi/ > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-961) Please delete old releases from mirroring system
Sebb created NIFI-961: - Summary: Please delete old releases from mirroring system Key: NIFI-961 URL: https://issues.apache.org/jira/browse/NIFI-961 Project: Apache NiFi Issue Type: Bug Reporter: Sebb To reduce the load on the ASF mirrors, projects are required to delete old releases [1] Please can you remove all non-current releases? i.e. all except 0.2.1 The earlier releases can still be mentioned on the download page, but the links should point to the archive server, i.e. http://archive.apache.org/dist/nifi/ Thanks! [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-960) Hashes, keys and sigs must be downloaded from the ASF mirror source
Sebb created NIFI-960: - Summary: Hashes, keys and sigs must be downloaded from the ASF mirror source Key: NIFI-960 URL: https://issues.apache.org/jira/browse/NIFI-960 Project: Apache NiFi Issue Type: Bug Reporter: Sebb The download page links to KEYS, hashes and sigs, which is good. However, it links to the release area in SVN, which is the wrong place. They should be downloaded from the ASF mirror source which is http://www.apache.org/dist/nifi The www.apache.org systems are set up for higher traffic levels and are mirrored in EU and US. The SVN dist system is not intended for downloading files by 3rd parties - it is the staging area from which the main ASF hosts are populated. Please update the download page to correct the links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-959) PutSolrContentStream not handling expression correctly for Collection property
Bryan Bende created NIFI-959: Summary: PutSolrContentStream not handling expression correctly for Collection property Key: NIFI-959 URL: https://issues.apache.org/jira/browse/NIFI-959 Project: Apache NiFi Issue Type: Bug Affects Versions: 0.3.0 Reporter: Bryan Bende Assignee: Bryan Bende Priority: Minor Fix For: 0.4.0 The Collection property in the Solr processors supports expression language, and the PutSolrContentStream processor is supposed to support receiving the Collection value from the incoming FlowFiles and be able to send to different collections from the same processor. The processor is evaluating the wrong value when calling context.getProperty(..).evaluateAttributeExpressions() for the Collection, which is causing this not to work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
svn commit: r10521 - in /dev/nifi/nifi-0.3.0: nifi-0.3.0-bin.tar.gz nifi-0.3.0-bin.zip
Author: mcgilman Date: Tue Sep 15 19:07:00 2015 New Revision: 10521 Log: adding binaries for 030 Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz (with props) dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip (with props) Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz == Binary file - no diff available. Propchange: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz -- svn:mime-type = application/octet-stream Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip == Binary file - no diff available. Propchange: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip -- svn:mime-type = application/octet-stream
[jira] [Commented] (NIFI-934) Image content viewer
[ https://issues.apache.org/jira/browse/NIFI-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745930#comment-14745930 ] Joseph Percivall commented on NIFI-934: --- Looks good, only comment is when there is an image with white near the edges (or the image is just white) it blends into the background and looks like nothing is there. Could add an option to display a border. > Image content viewer > > > Key: NIFI-934 > URL: https://issues.apache.org/jira/browse/NIFI-934 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Minor > Fix For: 0.4.0 > > Attachments: 0001-NIFI-934.patch > > > Add a new content viewer for images. This will allow us to view the images in > the application when they are the content of a flowfile. Should handle PNG, > JPEG, and GIF to start with. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
svn commit: r10520 - in /dev/nifi/nifi-0.3.0: nifi-0.3.0-bin.tar.gz.asc nifi-0.3.0-bin.tar.gz.md5 nifi-0.3.0-bin.tar.gz.sha1 nifi-0.3.0-bin.zip.md5 nifi-0.3.0-bin.zip.sha1
Author: mcgilman Date: Tue Sep 15 16:33:21 2015 New Revision: 10520 Log: adding binaries for 030 Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.asc dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.md5 dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.sha1 dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.md5 dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.sha1 Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.asc == --- dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.asc (added) +++ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.asc Tue Sep 15 16:33:21 2015 @@ -0,0 +1,17 @@ +-BEGIN PGP SIGNATURE- +Version: GnuPG v1 + +iQIcBAABAgAGBQJV944cAAoJEN9h7BlDKu43nGsQAKOMNiGaYUzcel9LDGHp4VLy +vHlADgy4iD/oYzw1c48tTR2N2xnc18IC1ilXSZokA6jVz8vIbMFdd83R40oRxhGK +Ji+Jfl9YA4zREjWxkO6zUJfRW8rKnM+CQ8O0uMZnumWP6mIrZwNsU/RJJ/sVARik +hyX9L1kUGFhyfR+g1xGQH6AwgAe0uFFshsUs1bWmYBjEzNADIzGuyj6lb9vcEqSd +okm4tb9nnOuONtWP62y8o+SCG3EBm91kmIMOCldESzrA4TZnInPo3nC9M0Vccdkc +YC1kWajV8ieNDSl2zVvrTaD35moTRImPNcNopf3fQXACXvV4m9+TluomvSy05VdG +ugMCVpQbe9o8Gc2PaOOWnaopmlMbv4+wYpxZtVT8LGwnosWxBRs7Xt6rnjGNiLII +Xw07dNfhNi028gbNiS0qRvvjir9rHwGx3bvx3Ndfoxhp07Q6gQFaAl+DRskI1iyb +G8EjoWxHtcLmCiq+7b1iX8QpihKYM8ZLjPToAYwHSgif7h/W83BzTgu2JJBCofCf +COCmusq1mUj+QmgXFZC3vrEjcD1A0rvmFfhUHXVSbxFzT0NXTn2fp0AwhFx2MtsQ +WpTannjuaVSx0Q2wRr8InsJK9nmVwn/PilK6Mkq5+xbw+hJUtZfOYyR7NNh13hQN +fVyfJidmSYXd9tBpX22g +=3UCT +-END PGP SIGNATURE- Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.md5 == --- dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.md5 (added) +++ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.md5 Tue Sep 15 16:33:21 2015 @@ -0,0 +1 @@ +a236dc1a2fcc44aa1e11c701ab474829 Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.sha1 == --- dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.sha1 (added) +++ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.tar.gz.sha1 Tue Sep 15 16:33:21 2015 @@ -0,0 +1 @@ +ffca9b60749ea9ba55ea3a381177f107890b70ba Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.md5 == --- dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.md5 (added) +++ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.md5 Tue Sep 15 16:33:21 2015 @@ -0,0 +1 @@ +e19e65ae05938fadaca234b2b9910623 Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.sha1 == --- dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.sha1 (added) +++ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.sha1 Tue Sep 15 16:33:21 2015 @@ -0,0 +1 @@ +f1fcbb04555c0ab2b14bcdfe2549c4c889a84472
svn commit: r10519 - in /dev/nifi/nifi-0.3.0: ./ nifi-0.3.0-bin.zip.asc
Author: mcgilman Date: Tue Sep 15 16:32:13 2015 New Revision: 10519 Log: adding binaries for 030 Added: dev/nifi/nifi-0.3.0/ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.asc Added: dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.asc == --- dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.asc (added) +++ dev/nifi/nifi-0.3.0/nifi-0.3.0-bin.zip.asc Tue Sep 15 16:32:13 2015 @@ -0,0 +1,17 @@ +-BEGIN PGP SIGNATURE- +Version: GnuPG v1 + +iQIcBAABAgAGBQJV944BAAoJEN9h7BlDKu43q4QP/RUH2yfFwZrGDBtOnYMRaUQ2 +p5vcfO0dt6xoOD1fhJa9LFAPyG+mghNWbuNZ5b3Y3yIyOeAnJSngNdDvdiOficWI +Ay+QDldXZyF43+GQbvpWYfHo9P/D6sx3aivvV5ra8lp4t9El6c/aKjluL7sXdXQY +KpCRWWawrtsWSjy/lYWn3X169BtFQgqMLYzEKR6/uChkU2qqo6KXzjT8pprh8JQA +u0x9W3cMT35rOPDuZ8OThhpMiST2bFmS4xQ+hOQ47ZQGdAT6cR1zI+Pa1AWAmvwR +tAme7u3ugbNImtOj5eXo8VRnVcDfpbgi0yknyzyGiNkIVgLRm4quV/ZNfvA42Cj1 +eiawlb7kFa99lz+fq4QENH4CUS43ml2Dc/XfznAHy+JwtnucvRJhlTAGQnQ5Q8Fn +P9nb4vtA0J/B2CNLUoXCE2zuI/TqDUVybbRV9PpGyc1vx8CUI+/S+wCMF1Soq0Df +WQtXg61Gsc2IlvNOr9p8Z+FmOh/ji9W4dOX0fs+kdkR0pEGItXM115VZPVNAhKPB +70NN4ypM+tFB2kKL5zvZtm/RrZDvYse247tjVOAJ4RqqMiVdnCnnE1QIrJggFD7N +jrrw6ahtwWjx7wukInfVZLdSux65MrXg4VVrvK+rIrKALAj0OCbF5wU9b0VhCl95 +TdorFYgiL+gj9ChWNYLj +=wi8p +-END PGP SIGNATURE-
[jira] [Updated] (NIFI-709) Add a PutSolr processor that supports Avro
[ https://issues.apache.org/jira/browse/NIFI-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-709: - Fix Version/s: (was: 0.4.0) > Add a PutSolr processor that supports Avro > -- > > Key: NIFI-709 > URL: https://issues.apache.org/jira/browse/NIFI-709 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > > The existing PutSolrContentStream is great for streaming json, xml, and csv > content directly to Solr, but it would be nice to also directly support Avro > since this will be a very common data format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-934) Image content viewer
[ https://issues.apache.org/jira/browse/NIFI-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-934: - Attachment: 0001-NIFI-934.patch > Image content viewer > > > Key: NIFI-934 > URL: https://issues.apache.org/jira/browse/NIFI-934 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Minor > Fix For: 0.4.0 > > Attachments: 0001-NIFI-934.patch > > > Add a new content viewer for images. This will allow us to view the images in > the application when they are the content of a flowfile. Should handle PNG, > JPEG, and GIF to start with. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
