[jira] [Commented] (NIFI-4753) Add Get Kudu Processor

[Sri Sai Kumar Ravipati (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321535#comment-16321535
 ] 

Sri Sai Kumar Ravipati commented on NIFI-4753:
--

Thanks [~mcgilman]

> Add Get Kudu Processor
> --
>
> Key: NIFI-4753
> URL: https://issues.apache.org/jira/browse/NIFI-4753
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Sri Sai Kumar Ravipati
>Assignee: Sri Sai Kumar Ravipati
>
> Now that we have the Put Kudu processor service currently in master, it would 
> be nice to have Get Kudu processor as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4715) ListS3 produces duplicates in frequently updated buckets

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321660#comment-16321660
 ] 

ASF GitHub Bot commented on NIFI-4715:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/2361
  
Thank you, @adamlamar I understand that.


> ListS3 produces duplicates in frequently updated buckets
> 
>
> Key: NIFI-4715
> URL: https://issues.apache.org/jira/browse/NIFI-4715
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0, 1.3.0, 1.4.0
> Environment: All
>Reporter: Milan Das
> Attachments: List-S3-dup-issue.xml, screenshot-1.png
>
>
> ListS3 state is implemented using HashSet. HashSet is not thread safe. When 
> ListS3 operates in multi threaded mode, sometimes it  tries to list  same 
> file from S3 bucket.  Seems like HashSet data is getting corrupted.
> currentKeys = new HashSet<>(); // need to be implemented Thread Safe like 
> currentKeys = //ConcurrentHashMap.newKeySet();
> *{color:red}+Update+{color}*:
> This is not a HashSet issue:
> Root cause is: 
> When the file gets uploaded to S3 simultaneously  when List S3 is in progress.
> onTrigger-->  maxTimestamp is initiated as 0L.
> This is clearing keys as per the code below
> When lastModifiedTime on S3 object is same as currentTimestamp for the listed 
> key it should be skipped. As the key is cleared, it is loading the same file 
> again. 
> I think fix should be to initiate the maxTimestamp with currentTimestamp not 
> 0L.
> {code}
>  long maxTimestamp = currentTimestamp;
> {code}
> Following block is clearing keys.
> {code:title=org.apache.nifi.processors.aws.s3.ListS3.java|borderStyle=solid}
>  if (lastModified > maxTimestamp) {
> maxTimestamp = lastModified;
> currentKeys.clear();
> getLogger().debug("clearing keys");
> }
> {code}
> Update: 01/03/2018
> There is one more flavor of same defect.
> Suppose: file1 is modified at 1514987611000 on S3 and currentTimestamp = 
> 1514987311000 on state.
> 1. File will be picked up time current state will be updated to 
> currentTimestamp=1514987311000 (but OS System time is 1514987611000)
> 2. next cycle for file2 with lastmodified: 1514987611000 : keys will be 
> cleared because lastModified > maxTimeStamp 
> (=currentTimestamp=1514987311000). 
> CurrentTimeStamp will saved as 1514987611000
> 3. next cycle: currentTimestamp=1514987611000 , "file1 modified at 
> 1514987611000" will be picked up again because file1 is no longer in the keys.
> I think solution is currentTimeStamp need to persisted current system time 
> stamp.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2361: NIFI-4715: ListS3 produces duplicates in frequently update...

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/2361
  
Thank you, @adamlamar I understand that.


---

[jira] [Commented] (NIFIREG-77) Allow a user to see the changes created by the currently loaded version

[Danny Lane (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319969#comment-16319969
 ] 

Danny Lane commented on NIFIREG-77:
---

Thanks [~bbende], that's helpful.
I had seen the NiFi code around the creating the FlowComparator and mapping to 
the DTOs but like you said, i was still trying to work out what the response 
from the new end-point should be.

At the moment it looks like most that I can see (all?) of the responses from 
the {{nifi-registry-web-api}} and {{nifi-registry-client}} are types from 
{{nifi-registry-data-model}}, {{FlowDifference}} isn't in the model module. Is 
there any issue with this? and adding {{nifi-registry-flow-diff}} as a 
dependency to both the api and client? This may be fine, I just wanted to 
confirm I wasn't breaking the pattern.
What I was thinking about before I read your comment above was to put the 
FlowComparator logic in {{org.apache.nifi.registry.service.RegistryService}} 
and map to/return new types in the data-model module. so the client & api 
wouldn't need new references to the diff module. This might not even be an 
issue?
I'm happy enough to go either route, let me know what you prefer and I'll start 
putting something together. 


> Allow a user to see the changes created by the currently loaded version
> ---
>
> Key: NIFIREG-77
> URL: https://issues.apache.org/jira/browse/NIFIREG-77
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Joseph Percivall
>Priority: Critical
> Attachments: Suggestion for diff UX.png
>
>
> As a user, I would like to see the changes that are included in a particular 
> version. More specifically, if I'm on an old version and I upgrade to a 
> version written by someone else, I have no way to know what changes occurred 
> during that version upgrade.
> A simple solution would be to utilize the same logic which displays the 
> current differences between local and stored in the registry and use that to 
> show the differences between the current version N and version N-1. The user 
> could then change between versions to see the changes that happened as part 
> of that version.
> An even better solution (from a DFM perspective) would be to be able to see 
> the changes within any version (not just the most recent). That way a DFM 
> wouldn't have to stop the flow for an extended period of time to view the 
> changes/differences in different versions but I think that'd be more work.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-342) MQTT framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320084#comment-16320084
 ] 

ASF GitHub Bot commented on MINIFICPP-342:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/228


> MQTT framework
> --
>
> Key: MINIFICPP-342
> URL: https://issues.apache.org/jira/browse/MINIFICPP-342
> Project: NiFi MiNiFi C++
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: bqiu
>Assignee: bqiu
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4763) Versioned Flows show as dirty when component versions change

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320390#comment-16320390
 ] 

ASF GitHub Bot commented on NIFI-4763:
--

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi/pull/2393

NIFI-4763: Ignore differences in components' Bundle Version when comp…

…aring a local flow to a flow in the registry

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/markap14/nifi NIFI-4763

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2393.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2393


commit 895163799df09e6ceffbd0bbee4398e638969135
Author: Mark Payne 
Date:   2018-01-10T15:01:27Z

NIFI-4763: Ignore differences in components' Bundle Version when comparing 
a local flow to a flow in the registry




> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2393: NIFI-4763: Ignore differences in components' Bundle...

[markap14]

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi/pull/2393

NIFI-4763: Ignore differences in components' Bundle Version when comp…

…aring a local flow to a flow in the registry

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/markap14/nifi NIFI-4763

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2393.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2393


commit 895163799df09e6ceffbd0bbee4398e638969135
Author: Mark Payne 
Date:   2018-01-10T15:01:27Z

NIFI-4763: Ignore differences in components' Bundle Version when comparing 
a local flow to a flow in the registry




---

[jira] [Created] (NIFI-4762) unable to use groovy from InvokeScriptedProcessor

[Martin Mucha (JIRA)]

Martin Mucha created NIFI-4762:
--

 Summary: unable to use groovy from InvokeScriptedProcessor
 Key: NIFI-4762
 URL: https://issues.apache.org/jira/browse/NIFI-4762
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.4.0
Reporter: Martin Mucha



Having following groovy, which just creates flowfile with sample json. 
Processor is configured such that it has script body in scriptBody property, 
while other property is empty.

{code:groovy}


import org.apache.nifi.processor.AbstractProcessor
import org.apache.nifi.processor.ProcessContext
import org.apache.nifi.processor.ProcessSession
import org.apache.nifi.processor.Relationship
import org.apache.nifi.processor.io.OutputStreamCallback

class GenerateJsonProcessor extends AbstractProcessor{

def REL_SUCCESS = new 
Relationship.Builder().name("success").description('FlowFiles that were 
successfully processed are routed here').build()

@Override
Set getRelationships() {
return Collections.singleton(REL_SUCCESS)
}

@Override
void onTrigger(ProcessContext context, ProcessSession session) {
def newFlowFile = session.create()
def json = "{}"

session.write(newFlowFile, new OutputStreamCallback() {
@Override
void process(OutputStream out) throws IOException {
def writer = new OutputStreamWriter(out);
writer.write(json)
writer.close()
}
})

session.transfer(newFlowFile, REL_SUCCESS)
//session.commit()
}
}

processor = new GenerateJsonProcessor()

{code}


produces following error:


{code:log}
java.lang.reflect.UndeclaredThrowableException: null
at com.sun.proxy.$Proxy137.validate(Unknown Source)
at 
org.apache.nifi.processors.script.InvokeScriptedProcessor.customValidate(InvokeScriptedProcessor.java:465)
at 
org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
at 
org.apache.nifi.controller.AbstractConfiguredComponent.validate(AbstractConfiguredComponent.java:329)
at 
org.apache.nifi.controller.StandardProcessorNode.isValid(StandardProcessorNode.java:969)
at 
org.apache.nifi.controller.FlowController.getProcessorStatus(FlowController.java:2976)
at 
org.apache.nifi.controller.FlowController.getGroupStatus(FlowController.java:2571)
at 
org.apache.nifi.controller.FlowController.getGroupStatus(FlowController.java:2513)
at 
org.apache.nifi.controller.FlowController.getGroupStatus(FlowController.java:2485)
at 
org.apache.nifi.controller.FlowController.getControllerStatus(FlowController.java:2473)
at 
org.apache.nifi.reporting.SiteToSiteProvenanceReportingTask.onTrigger(SiteToSiteProvenanceReportingTask.java:227)
at 
org.apache.nifi.controller.tasks.ReportingTaskWrapper.run(ReportingTaskWrapper.java:41)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.script.ScriptException: java.lang.NullPointerException
at 
org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.invokeImpl(GroovyScriptEngineImpl.java:405)
at 
org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.access$100(GroovyScriptEngineImpl.java:98)
at 
org.codehaus.groovy.jsr223.GroovyScriptEngineImpl$3.invoke(GroovyScriptEngineImpl.java:446)
... 19 common frames omitted
Caused by: java.lang.NullPointerException: null
at java.io.File.(File.java:277)
at 
org.apache.nifi.processor.util.StandardValidators$FileExistsValidator.validate(StandardValidators.java:784)
at 
org.apache.nifi.components.PropertyDescriptor.validate(PropertyDescriptor.java:200)
at 
org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:116)
at sun.reflect.GeneratedMethodAccessor489.invoke(Unknown Source)

{code}

where error lies outside of written code. I'd assume, that this line:
org.apache.nifi.processor.util.StandardValidators$FileExistsValidator.validate(StandardValidators.java:784)

is the most relevant from this stacktrace. Why are we validating `null` valued 
file for existence?




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4760) TestListenSMTP tests fail on OSX

[Marco Gaido (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320322#comment-16320322
 ] 

Marco Gaido commented on NIFI-4760:
---

Thanks [~jzemerick], on my host it works perfectly run anyway and my config is 
very close to your:

Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
2017-04-03T21:39:06+02:00)
Maven home: /usr/local/Cellar/maven/3.5.0/libexec
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.1", arch: "x86_64", family: "mac"

It may be a problem in sending data. The timeout is 5 seconds, and if a 
connection is failing in your case, it will hang for 1 minute. So this is a 
possibility. But it's hard to say without further info.

> TestListenSMTP tests fail on OSX
> 
>
> Key: NIFI-4760
> URL: https://issues.apache.org/jira/browse/NIFI-4760
> Project: Apache NiFi
>  Issue Type: Test
>Affects Versions: 1.5.0
>Reporter: Jeff Zemerick
>Priority: Minor
>
> When building 1.5.0 on OSX High Sierra with the following command:
> mvn clean install -Pcontrib-check
> (At first I thought it was because I was doing -T 1C but it fails without 
> parallel, too.)
> Some tests in TestListenSMTP reliably fail:
> Results :
> Failed tests: 
>   TestListenSMTP.validateSuccessfulInteraction:88
>   TestListenSMTP.validateSuccessfulInteractionWithTls:150
>   TestListenSMTP.validateTooLargeMessage:192
> The relevant test output:
> validateSuccessfulInteraction(org.apache.nifi.processors.email.TestListenSMTP)
>   Time elapsed: 15.069 sec  <<< FAILURE!
> java.lang.AssertionError
>   at 
> org.apache.nifi.processors.email.TestListenSMTP.validateSuccessfulInteraction(TestListenSMTP.java:88)
> validateSuccessfulInteractionWithTls(org.apache.nifi.processors.email.TestListenSMTP)
>   Time elapsed: 16.514 sec  <<< FAILURE!
> java.lang.AssertionError
>   at 
> org.apache.nifi.processors.email.TestListenSMTP.validateSuccessfulInteractionWithTls(TestListenSMTP.java:150)
> validateTooLargeMessage(org.apache.nifi.processors.email.TestListenSMTP)  
> Time elapsed: 21.516 sec  <<< FAILURE!
> java.lang.AssertionError
>   at 
> org.apache.nifi.processors.email.TestListenSMTP.validateTooLargeMessage(TestListenSMTP.java:192)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4763) Versioned Flows show as dirty when component versions change

[Bryan Bende (JIRA)]

Bryan Bende created NIFI-4763:
-

 Summary: Versioned Flows show as dirty when component versions 
change
 Key: NIFI-4763
 URL: https://issues.apache.org/jira/browse/NIFI-4763
 Project: Apache NiFi
  Issue Type: Improvement
Affects Versions: 1.5.0
Reporter: Bryan Bende
Priority: Minor


While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
bunch of example versioned flows. I upgraded this instance by replacing the lib 
directory with everything from the 1.5.0 RC.

When I went to the UI I noticed all the versioned PGs were showing local 
changes. Looking at one of them it was because the local flow had upgraded all 
the component versions to 1.5.0, but the last version of that flow in the 
registry had the components at 1.5.0-SNAPSHOT.

At this point you can try to rollback the local changes, but it can't really 
rollback because there are no more processors for 1.5.0-SNAPSHOT. You can save 
a new version of the flow with the new component versions and all is good.

This won't really be an issue until the next release when folks have already 
been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
next release is). We may want to ignore component version differences until 
sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4759) PutMongo fails when the update key is not _id

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320416#comment-16320416
 ] 

ASF GitHub Bot commented on NIFI-4759:
--

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2392
  
Thanks @mgaido91. Unfortunately, the user got back to me and told me they 
noticed another bug that is related to this so I have to expand on it. I'll 
incorporate your feedback into that.


> PutMongo fails when the update key is not _id
> -
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> This works:
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> This does not:
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2392: NIFI-4759 Fixed a bug that left a hard-coded reference to ...

[MikeThomsen]

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2392
  
Thanks @mgaido91. Unfortunately, the user got back to me and told me they 
noticed another bug that is related to this so I have to expand on it. I'll 
incorporate your feedback into that.


---

[jira] [Commented] (NIFI-4763) Versioned Flows show as dirty when component versions change

[Mark Payne (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320388#comment-16320388
 ] 

Mark Payne commented on NIFI-4763:
--

We should probably ignore differences in Bundle Versions for now. I can tackle 
that.

> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Priority: Minor
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (NIFI-4763) Versioned Flows show as dirty when component versions change

[Mark Payne (JIRA)]

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

Mark Payne reassigned NIFI-4763:


Assignee: Mark Payne

> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4763) Versioned Flows show as dirty when component versions change

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-4763:
-
Status: Patch Available  (was: Open)

> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4390) Add a keyboard shortcut for Connection related dialogs

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-4390:
---
Affects Version/s: (was: 1.3.0)
   Status: Patch Available  (was: Open)

> Add a keyboard shortcut for Connection related dialogs
> --
>
> Key: NIFI-4390
> URL: https://issues.apache.org/jira/browse/NIFI-4390
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Yuri
>Priority: Minor
>  Labels: dialogs, shortcuts, ui, ux
> Attachments: nifi_dialogs_v1.ods
>
>
> Current dialogs don't allow to bound a keyboard shortcut to an action. This 
> hinders the UX, since there are many dialogs involved in the most common 
> interactions.
> For instance, adding a new connection with a single relationship still 
> requires a click at the confirm button. Instead, it should be possible to 
> confirm the dialog simply by hitting the Enter key.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4764) Add tooltips to status bar icons

[Matt Burgess (JIRA)]

Matt Burgess created NIFI-4764:
--

 Summary: Add tooltips to status bar icons
 Key: NIFI-4764
 URL: https://issues.apache.org/jira/browse/NIFI-4764
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core UI
Reporter: Matt Burgess


The current status bar has a number of icons that refer to various states of 
components in the NiFi instance, and with NiFi Registry support in 1.5.0 there 
will be even more. Currently the documentation for these icons is in the User 
Guide, but it would nice to have tooltips for each icon (with its description 
and the count) so the information is readily available without having to go to 
the Help documentation in the UI.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MINIFICPP-365) Refine log levels

[Aldrin Piri (JIRA)]

Aldrin Piri created MINIFICPP-365:
-

 Summary: Refine log levels
 Key: MINIFICPP-365
 URL: https://issues.apache.org/jira/browse/MINIFICPP-365
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Aldrin Piri


minifi-app.log is verbose and includes a lot of information at an INFO level 
that is below the typical information a person might care to see.  Some 
statements are likely extraneous and remnants of development, some should be 
dropped to a lower priority and others seem duplicative.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (NIFI-4761) Allow whitelisting expected Host values

[Andy LoPresto (JIRA)]

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

Andy LoPresto reassigned NIFI-4761:
---

Assignee: Andy LoPresto

> Allow whitelisting expected Host values
> ---
>
> Key: NIFI-4761
> URL: https://issues.apache.org/jira/browse/NIFI-4761
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Andy LoPresto
>
> NiFi has been updated to only accept requests where the Host header contains 
> an expected value. Currently, the expected values are driven by the .host 
> properties in nifi.properties. When running behind a proxy, the value may be 
> the proxy host if the headers simply pass through. In this scenario, we 
> should offer the ability to whitelist values in case updating the proxy 
> configuration isn't possible.
> Also, the proxy documentation in the admin guide should be updated to include 
> details regarding the Host name whitelisting. Also, should verify the context 
> path whitelisting is documented there.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4759) PutMongo does not handle updateKey field correctly

[Mike Thomsen (JIRA)]

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

Mike Thomsen updated NIFI-4759:
---
Summary: PutMongo does not handle updateKey field correctly  (was: PutMongo 
fails when the update key is not _id)

> PutMongo does not handle updateKey field correctly
> --
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> This works:
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> This does not:
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4759) PutMongo fails when the update key is not _id

[Mike Thomsen (JIRA)]

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

Mike Thomsen updated NIFI-4759:
---
Description: 
This works:

{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}

This does not:

{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}



  was:
This works:

{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}

This does not:

{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}


> PutMongo fails when the update key is not _id
> -
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> This works:
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> This does not:
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4759) PutMongo does not handle updateKey field correctly

[Mike Thomsen (JIRA)]

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

Mike Thomsen updated NIFI-4759:
---
Description: 
This works:

{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}

This does not:

{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}


  was:
This works:

{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}

This does not:

{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}




> PutMongo does not handle updateKey field correctly
> --
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> This works:
> {code:java}
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> {code}
> This does not:
> {code:java}
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4761) Allow whitelisting expected Host values

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-4761:
--
Description: 
NiFi has been updated to only accept requests where the Host header contains an 
expected value. Currently, the expected values are driven by the .host 
properties in nifi.properties. When running behind a proxy, the value may be 
the proxy host if the headers simply pass through. In this scenario, we should 
offer the ability to whitelist values in case updating the proxy configuration 
isn't possible.

Also, the proxy documentation in the admin guide should be updated to include 
details regarding the Host name whitelisting. Also, should verify the context 
path whitelisting is documented there.

  was:NiFi has been updated to only accept requests where the Host header 
contains an expected value. Currently, the expected values are driven by the 
.host properties in nifi.properties. When running behind a proxy, the value may 
be the proxy host if the headers simply pass through. In this scenario, we 
should offer the ability to whitelist values in case updating the proxy 
configuration isn't possible.


> Allow whitelisting expected Host values
> ---
>
> Key: NIFI-4761
> URL: https://issues.apache.org/jira/browse/NIFI-4761
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>
> NiFi has been updated to only accept requests where the Host header contains 
> an expected value. Currently, the expected values are driven by the .host 
> properties in nifi.properties. When running behind a proxy, the value may be 
> the proxy host if the headers simply pass through. In this scenario, we 
> should offer the ability to whitelist values in case updating the proxy 
> configuration isn't possible.
> Also, the proxy documentation in the admin guide should be updated to include 
> details regarding the Host name whitelisting. Also, should verify the context 
> path whitelisting is documented there.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4759) PutMongo does not handle updateKey field correctly

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320740#comment-16320740
 ] 

ASF GitHub Bot commented on NIFI-4759:
--

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2392
  
@mgaido91 
@mattyb149 

Ok, added a UT that really kicks the tires on both problems. I updated the 
ticket with a new title and an explanation of both issues. Most of the code 
here is focused on handling ObjectIDs correctly.

https://issues.apache.org/jira/browse/NIFI-4759


> PutMongo does not handle updateKey field correctly
> --
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> Two issues:
> * The updateKey field is ignored in favor of _id in the update code block of 
> PutMongo.
> * _id fields are always treated as strings, even if they're valid ObjectIds 
> represented as a string. PutMongo should be able to handle these as ObjectIds.
> Regarding the first point, this works:
> {code:java}
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> {code}
> This does not:
> {code:java}
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4753) Add Get Kudu Processor

[Sri Sai Kumar Ravipati (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320865#comment-16320865
 ] 

Sri Sai Kumar Ravipati commented on NIFI-4753:
--

Hi [~joewitt], Can you assign this task to me?

> Add Get Kudu Processor
> --
>
> Key: NIFI-4753
> URL: https://issues.apache.org/jira/browse/NIFI-4753
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Sri Sai Kumar Ravipati
>
> Now that we have the Put Kudu processor service currently in master, it would 
> be nice to have Get Kudu processor as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2392: NIFI-4759 Fixed a bug that left a hard-coded reference to ...

[MikeThomsen]

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2392
  
@mgaido91 
@mattyb149 

Ok, added a UT that really kicks the tires on both problems. I updated the 
ticket with a new title and an explanation of both issues. Most of the code 
here is focused on handling ObjectIDs correctly.

https://issues.apache.org/jira/browse/NIFI-4759


---

[jira] [Updated] (NIFI-4759) PutMongo does not handle updateKey field correctly

[Mike Thomsen (JIRA)]

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

Mike Thomsen updated NIFI-4759:
---
Description: 
Two issues:

* The updateKey field is ignored in favor of _id in the update code block of 
PutMongo.
* _id fields are always treated as strings, even if they're valid ObjectIds 
represented as a string. PutMongo should be able to handle these as ObjectIds.

This works:

{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}

This does not:

{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}


  was:
This works:

{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}

This does not:

{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}



> PutMongo does not handle updateKey field correctly
> --
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> Two issues:
> * The updateKey field is ignored in favor of _id in the update code block of 
> PutMongo.
> * _id fields are always treated as strings, even if they're valid ObjectIds 
> represented as a string. PutMongo should be able to handle these as ObjectIds.
> This works:
> {code:java}
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> {code}
> This does not:
> {code:java}
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4759) PutMongo does not handle updateKey field correctly

[Mike Thomsen (JIRA)]

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

Mike Thomsen updated NIFI-4759:
---
Description: 
Two issues:

* The updateKey field is ignored in favor of _id in the update code block of 
PutMongo.
* _id fields are always treated as strings, even if they're valid ObjectIds 
represented as a string. PutMongo should be able to handle these as ObjectIds.

Regarding the first point, this works:

{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}

This does not:

{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}


  was:
Two issues:

* The updateKey field is ignored in favor of _id in the update code block of 
PutMongo.
* _id fields are always treated as strings, even if they're valid ObjectIds 
represented as a string. PutMongo should be able to handle these as ObjectIds.

This works:

{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}

This does not:

{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}



> PutMongo does not handle updateKey field correctly
> --
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>
> Two issues:
> * The updateKey field is ignored in favor of _id in the update code block of 
> PutMongo.
> * _id fields are always treated as strings, even if they're valid ObjectIds 
> represented as a string. PutMongo should be able to handle these as ObjectIds.
> Regarding the first point, this works:
> {code:java}
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> {code}
> This does not:
> {code:java}
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp issue #231: MINIFICPP-359 Generate connection name field if ...

[achristianson]

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/231
  
@phrocker fixed conflct should be ready for re-review.


---

[jira] [Resolved] (MINIFICPP-342) MQTT framework

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-342.
--
Resolution: Fixed

> MQTT framework
> --
>
> Key: MINIFICPP-342
> URL: https://issues.apache.org/jira/browse/MINIFICPP-342
> Project: NiFi MiNiFi C++
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: bqiu
>Assignee: bqiu
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-registry issue #81: NIFIREG-108 Change REST API buckets ordering

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/81
  
Looks good, going to merge


---

[jira] [Commented] (NIFIREG-108) REST API should return alphabetical ordering for lists of buckets

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320504#comment-16320504
 ] 

ASF GitHub Bot commented on NIFIREG-108:


Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/81


> REST API should return alphabetical ordering for lists of buckets
> -
>
> Key: NIFIREG-108
> URL: https://issues.apache.org/jira/browse/NIFIREG-108
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 0.1.1
>
> Attachments: buckets-dropdown.jpg
>
>
> The response of GET /buckets is a list of buckets to which the current user 
> as access. It should be alphabetically ordered. This will provide a better 
> experience when buckets are presented in drop down list, such as in the NiFi 
> Registry UI filter:
> !buckets-dropdown.jpg|thumbnail!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2394: NIFI-4764: Add tooltips to status bar icons

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2394
  
Thanks for submitting a PR for this @mgaido91! Would you be able to also 
update the tooltips on the icons on the Process Group node on the canvas? They 
should be in nf-process-group.js.

Thanks!


---

[jira] [Commented] (NIFI-4764) Add tooltips to status bar icons

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320643#comment-16320643
 ] 

ASF GitHub Bot commented on NIFI-4764:
--

Github user mgaido91 commented on the issue:

https://github.com/apache/nifi/pull/2394
  
@mcgilman yes, sure, thanks for your comment. Just one question before 
proceeding. Doing this might involve some refactoring/non-trivial js, since 
process groups are in the canvas and therefore `title` doesn't work. Is it ok?


> Add tooltips to status bar icons
> 
>
> Key: NIFI-4764
> URL: https://issues.apache.org/jira/browse/NIFI-4764
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Burgess
>
> The current status bar has a number of icons that refer to various states of 
> components in the NiFi instance, and with NiFi Registry support in 1.5.0 
> there will be even more. Currently the documentation for these icons is in 
> the User Guide, but it would nice to have tooltips for each icon (with its 
> description and the count) so the information is readily available without 
> having to go to the Help documentation in the UI.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2394: NIFI-4764: Add tooltips to status bar icons

[mgaido91]

Github user mgaido91 commented on the issue:

https://github.com/apache/nifi/pull/2394
  
@mcgilman yes, sure, thanks for your comment. Just one question before 
proceeding. Doing this might involve some refactoring/non-trivial js, since 
process groups are in the canvas and therefore `title` doesn't work. Is it ok?


---

[jira] [Commented] (NIFI-4764) Add tooltips to status bar icons

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320653#comment-16320653
 ] 

ASF GitHub Bot commented on NIFI-4764:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2394
  
The change should be pretty straight forward. Here is an example of setting 
the title on the SVG elements [1]. In this example however, the tooltip is 
dynamic and needs to be regularly updated. Your tooltips will be not be 
changing based on the configuration so you only need to set them when those 
elements are appended starting here [2].

[1] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-process-group.js#L1195
[2] 
https://github.com/apache/nifi/blob/6153fb64655701f7bfdaadfe1ff7c8def111422c/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-process-group.js#L304


> Add tooltips to status bar icons
> 
>
> Key: NIFI-4764
> URL: https://issues.apache.org/jira/browse/NIFI-4764
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Burgess
>
> The current status bar has a number of icons that refer to various states of 
> components in the NiFi instance, and with NiFi Registry support in 1.5.0 
> there will be even more. Currently the documentation for these icons is in 
> the User Guide, but it would nice to have tooltips for each icon (with its 
> description and the count) so the information is readily available without 
> having to go to the Help documentation in the UI.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2394: NIFI-4764: Add tooltips to status bar icons

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2394
  
The change should be pretty straight forward. Here is an example of setting 
the title on the SVG elements [1]. In this example however, the tooltip is 
dynamic and needs to be regularly updated. Your tooltips will be not be 
changing based on the configuration so you only need to set them when those 
elements are appended starting here [2].

[1] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-process-group.js#L1195
[2] 
https://github.com/apache/nifi/blob/6153fb64655701f7bfdaadfe1ff7c8def111422c/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-process-group.js#L304


---

[GitHub] nifi-registry issue #80: [NIFIREG-99] add refresh button to an items change ...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/80
  
Looks good, will merge


---

[jira] [Commented] (NIFI-4588) Add ability to use update operators like $set and $push in PutMongo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319964#comment-16319964
 ] 

ASF GitHub Bot commented on NIFI-4588:
--

Github user dyunggertrude commented on the issue:

https://github.com/apache/nifi/pull/2259
  
Hi,
I need some help

I try to use putMongo 1.5.0 with the ability to not replacing the whole 
collection (option With operators enabled in Update Mode)


![image](https://user-images.githubusercontent.com/32461359/34765326-72512c26-f5f1-11e7-9d32-d0def0f01713.png)
the flow file is like this :
{  "$set": {
"type":"Cc",
"nmess":14488,
   "idgtr":"C-0--00088--0-CMF-RMF",
"last_update":"2018-01-10T09:32:35",
"libelle":"Bonifacio_Estefan.   " }
}

When i launch nifi process,   attributes not listed in my flow are deleted 
!!!

What's wrong in my configuration



> Add ability to use update operators like $set and $push in PutMongo
> ---
>
> Key: NIFI-4588
> URL: https://issues.apache.org/jira/browse/NIFI-4588
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
> Fix For: 1.5.0
>
>
> The current implementation of PutMongo just puts an entire document in with 
> an update. There are situations where this will definitely not work like when 
> a user needs to just update one field or push an element to array in an 
> existing document.
> The update should provide a configurable ability to push either an entire 
> JSON document (using extended JSON, as that is required by MongoDB) or use an 
> update document like this:
> {code:java}
> {
> "$set": {
> "strField": "Message",
> "dateField": {
>  "$date": 1510235376611
>  }
> },
> "$push": {
> "arrayField": {
> "field": "Something here"
> }
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #234: MINIFICPP-363 Allow for unqualified class...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/234


---

[jira] [Commented] (MINIFICPP-363) Allow for unqualified class names in YAML configuration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320064#comment-16320064
 ] 

ASF GitHub Bot commented on MINIFICPP-363:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/234


> Allow for unqualified class names in YAML configuration
> ---
>
> Key: MINIFICPP-363
> URL: https://issues.apache.org/jira/browse/MINIFICPP-363
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Minor
>
> Current configurations require processor class names that look like this:
> {code}
> org.apache.nifi.processors.standard.GenerateFlowFile
> {code}
> This is extremely verbose and essentially only is there to support configs 
> converted from Java. The class names currently have no meaning in the cpp 
> codebase.
> Allowing unqualified classes will help simplify hand-configured YAML 
> configurations and make things easier to read. New configurations would 
> support classes specified as such:
> {code}
> GenerateFlowFile
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (NIFI-4753) Add Get Kudu Processor

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-4753:
-

Assignee: Matt Gilman

> Add Get Kudu Processor
> --
>
> Key: NIFI-4753
> URL: https://issues.apache.org/jira/browse/NIFI-4753
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Sri Sai Kumar Ravipati
>Assignee: Matt Gilman
>
> Now that we have the Put Kudu processor service currently in master, it would 
> be nice to have Get Kudu processor as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-118) Dynamic Properties support for processors

[Andrew Christianson (JIRA)]

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

Andrew Christianson updated MINIFICPP-118:
--
Fix Version/s: 0.4.0

> Dynamic Properties support for processors
> -
>
> Key: MINIFICPP-118
> URL: https://issues.apache.org/jira/browse/MINIFICPP-118
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Jeremy Dyer
>Assignee: Andrew Christianson
> Fix For: 0.4.0
>
>
> Currently any Property read from the config.yml file that is not explicitly 
> defined in the processor's implementation will be ignored by Processor.cpp 
> when reading the configurations. This prevents any dynamic property from 
> being defined in the config.yml and passed to the processor at runtime. 
> Certain processors rely heavily on the concept of dynamic properties that are 
> passed to them at runtime to handle things like setting dynamic properties 
> based on properties that are declared. All of these possibilities cannot be 
> handled upfront so there should be a mechanism, most likely in Processor.cpp, 
> that allows for a list of dynamicProperties that are parsed form the 
> config.yml file to be stored and accessed by the underlying processor 
> implementation at runtime and use them as the processor desires.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-118) Dynamic Properties support for processors

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320895#comment-16320895
 ] 

ASF GitHub Bot commented on MINIFICPP-118:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/37
  
Taking this on.


> Dynamic Properties support for processors
> -
>
> Key: MINIFICPP-118
> URL: https://issues.apache.org/jira/browse/MINIFICPP-118
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Jeremy Dyer
>Assignee: Andrew Christianson
> Fix For: 0.4.0
>
>
> Currently any Property read from the config.yml file that is not explicitly 
> defined in the processor's implementation will be ignored by Processor.cpp 
> when reading the configurations. This prevents any dynamic property from 
> being defined in the config.yml and passed to the processor at runtime. 
> Certain processors rely heavily on the concept of dynamic properties that are 
> passed to them at runtime to handle things like setting dynamic properties 
> based on properties that are declared. All of these possibilities cannot be 
> handled upfront so there should be a mechanism, most likely in Processor.cpp, 
> that allows for a list of dynamicProperties that are parsed form the 
> config.yml file to be stored and accessed by the underlying processor 
> implementation at runtime and use them as the processor desires.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MINIFICPP-369) Implement multiple attribute expressions in expression language

[Andrew Christianson (JIRA)]

Andrew Christianson created MINIFICPP-369:
-

 Summary: Implement multiple attribute expressions in expression 
language
 Key: MINIFICPP-369
 URL: https://issues.apache.org/jira/browse/MINIFICPP-369
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Andrew Christianson


Evaluating Multiple Attributes
anyAttribute
allAttributes
anyMatchingAttribute
allMatchingAttributes
anyDelineatedValue
allDelineatedValues
join
count



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-358) Implement TFExtractTopLabels

[Andrew Christianson (JIRA)]

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

Andrew Christianson resolved MINIFICPP-358.
---
Resolution: Fixed

> Implement TFExtractTopLabels
> 
>
> Key: MINIFICPP-358
> URL: https://issues.apache.org/jira/browse/MINIFICPP-358
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>
> Add support for interpreting output tensors which represent labels with 
> scores. A list of labels in index order is passed in with attribute tf.type 
> == "labels". The top N labels are extracted into attributes tf.label. and 
> tf.score.. The tf.label.0 attribute represents the highest-scoring label 
> and can be used, for example, to route FlowFiles based on model inferences.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-365) Refine log levels

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated MINIFICPP-365:
--
Fix Version/s: 0.4.0

> Refine log levels
> -
>
> Key: MINIFICPP-365
> URL: https://issues.apache.org/jira/browse/MINIFICPP-365
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Aldrin Piri
> Fix For: 0.4.0
>
>
> minifi-app.log is verbose and includes a lot of information at an INFO level 
> that is below the typical information a person might care to see.  Some 
> statements are likely extraneous and remnants of development, some should be 
> dropped to a lower priority and others seem duplicative.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-registry issue #78: [NIFIREG-78] disable new policy option when registr...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/78
  
Looks good, will merge


---

[jira] [Updated] (MINIFICPP-355) Starting minifi on arm fails quietly

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-355:
-
Fix Version/s: 0.4.0

> Starting minifi on arm fails quietly
> 
>
> Key: MINIFICPP-355
> URL: https://issues.apache.org/jira/browse/MINIFICPP-355
> Project: NiFi MiNiFi C++
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: raspberry pi zero w - arm
>Reporter: Joseph Witt
>Assignee: marco polo
> Fix For: 0.4.0
>
> Attachments: config.yml, minifi-app.log
>
>
> During startup the process quietly dies.  Aldrin showed me the cool process 
> to gather more data
> gdb bin/minifi
> -> run
> -> backtrace
> which yields 
> {quote}
> [Thread 0xb0eff160 (LWP 24133) exited]
> [Thread 0xb2eff160 (LWP 24138) exited]
> Thread 1 "minifi" received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/arm/armv6/strlen.S:26
> 26../sysdeps/arm/armv6/strlen.S: No such file or directory.
> (gdb) backtrace
> #0  strlen () at ../sysdeps/arm/armv6/strlen.S:26
> #1  0xb64f0690 in _IO_vfprintf_internal (s=s@entry=0xbeffc3c0, 
> format=format@entry=0x609884 "Setting %d as the max queue size for %s", 
> ap=..., ap@entry=...)
> at vfprintf.c:1637
> #2  0xb6513d2c in _IO_vsnprintf (string=0xbeffc4f0 "Setting 0 as the max 
> queue size for p => [success]", maxlen=,
> format=0x609884 "Setting %d as the max queue size for %s", 
> format@entry=0xbeffcac8 "\330\033\207", args=..., args@entry=...) at 
> vsnprintf.c:114
> #3  0xb64f5b18 in __snprintf (s=, maxlen=, 
> format=0x609884 "Setting %d as the max queue size for %s") at snprintf.c:33
> #4  0x00284a4c in std::__cxx11::basic_string std::allocator > 
> org::apache::nifi::minifi::core::logging::format_string const*>(char const*, long long&&, char const*&&) [clone .isra.369] ()
> #5  0x00285dec in void 
> org::apache::nifi::minifi::core::logging::Logger::log std::__cxx11::basic_string > >(spdlog::level::level_enum, char const*, long long const&, 
> std::__cxx11::basic_string > const&) ()
> #6  0x0027efb4 in 
> org::apache::nifi::minifi::core::YamlConfiguration::parseConnectionYaml(YAML::Node*,
>  org::apache::nifi::minifi::core::ProcessGroup*) ()
> #7  0x0025ef3c in 
> org::apache::nifi::minifi::core::YamlConfiguration::getYamlRoot(YAML::Node*) 
> ()
> #8  0x0025f230 in 
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(std::__cxx11::basic_string  std::char_traits, std::allocator > const&) ()
> #9  0x002965b8 in org::apache::nifi::minifi::FlowController::load() ()
> #10 0x00161998 in main ()
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (NIFIREG-78) Bucket policies should be unavailable when running unsecured

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFIREG-78.

Resolution: Fixed

> Bucket policies should be unavailable when running unsecured
> 
>
> Key: NIFIREG-78
> URL: https://issues.apache.org/jira/browse/NIFIREG-78
> Project: NiFi Registry
>  Issue Type: Bug
>Affects Versions: 0.1.0
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 0.1.1
>
>
> As far as I'm aware, bucket policies are only used when the security settings 
> are enabled (same as the Users). If so, the UI should more clearly convey 
> this and the "NEW POLICY" button should be disabled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-324) Resolve RHEL7 build issues

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated MINIFICPP-324:
--
Fix Version/s: 0.4.0

> Resolve RHEL7 build issues
> --
>
> Key: MINIFICPP-324
> URL: https://issues.apache.org/jira/browse/MINIFICPP-324
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFIREG-78) Bucket policies should be unavailable when running unsecured

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFIREG-78:
---
Fix Version/s: 0.1.1

> Bucket policies should be unavailable when running unsecured
> 
>
> Key: NIFIREG-78
> URL: https://issues.apache.org/jira/browse/NIFIREG-78
> Project: NiFi Registry
>  Issue Type: Bug
>Affects Versions: 0.1.0
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 0.1.1
>
>
> As far as I'm aware, bucket policies are only used when the security settings 
> are enabled (same as the Users). If so, the UI should more clearly convey 
> this and the "NEW POLICY" button should be disabled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFIREG-78) Bucket policies should be unavailable when running unsecured

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320944#comment-16320944
 ] 

ASF GitHub Bot commented on NIFIREG-78:
---

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/78


> Bucket policies should be unavailable when running unsecured
> 
>
> Key: NIFIREG-78
> URL: https://issues.apache.org/jira/browse/NIFIREG-78
> Project: NiFi Registry
>  Issue Type: Bug
>Affects Versions: 0.1.0
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 0.1.1
>
>
> As far as I'm aware, bucket policies are only used when the security settings 
> are enabled (same as the Users). If so, the UI should more clearly convey 
> this and the "NEW POLICY" button should be disabled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-registry pull request #78: [NIFIREG-78] disable new policy option when ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/78


---

[jira] [Updated] (MINIFICPP-26) Timing out content claim causes state loss to persist and rollbacks to hinder progress.

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-26:

Fix Version/s: 0.3.0

> Timing out content claim causes state loss to persist and rollbacks to hinder 
> progress. 
> 
>
> Key: MINIFICPP-26
> URL: https://issues.apache.org/jira/browse/MINIFICPP-26
> Project: NiFi MiNiFi C++
>  Issue Type: Sub-task
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>
> Related to MINIFI-383 and MINIFI-384. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-27) Site to Site not using correct port when in/output are specified in yaml file

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-27:

Fix Version/s: 0.3.0

> Site to Site not using correct port when in/output are specified in yaml file
> -
>
> Key: MINIFICPP-27
> URL: https://issues.apache.org/jira/browse/MINIFICPP-27
> Project: NiFi MiNiFi C++
>  Issue Type: Sub-task
>Reporter: marco polo
>Assignee: marco polo
>Priority: Blocker
> Fix For: 0.3.0
>
>
> We end up blocking Site To Site because of exceptions on a full or invalid 
> output port if you have an output port specified that's not connected in the 
> flow. This will cause the site to site operations to be degraded severely. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-24) Event time not being set in FlowFile causing content to be removed prematurely.

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-24:

Fix Version/s: 0.3.0

> Event time not being set in FlowFile causing content to be removed 
> prematurely. 
> 
>
> Key: MINIFICPP-24
> URL: https://issues.apache.org/jira/browse/MINIFICPP-24
> Project: NiFi MiNiFi C++
>  Issue Type: Sub-task
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>
> Since no unit test exists for FF in MiNiFi C++ there is no test to see if 
> setters and getters exist or work for FlowFile. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-295) Import functions in ProcessSession should be moved to vector so we don't need to delete them

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-295.
--
Resolution: Duplicate

Resolved with MINIFICPP-293. 

> Import functions in ProcessSession should be moved to vector so we don't need 
> to delete them
> 
>
> Key: MINIFICPP-295
> URL: https://issues.apache.org/jira/browse/MINIFICPP-295
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>
> Should use the vector's destructor when the function exists to reclaim that 
> memory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-301) Create processor to apply arbitrary Tensor Flow graphs to tensors

[Aldrin Piri (JIRA)]

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

Aldrin Piri resolved MINIFICPP-301.
---
Resolution: Fixed

> Create processor to apply arbitrary Tensor Flow graphs to tensors
> -
>
> Key: MINIFICPP-301
> URL: https://issues.apache.org/jira/browse/MINIFICPP-301
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
> Fix For: 0.3.0
>
>
> In many cases, it may be desirable to interpret/preprocess raw signal inputs 
> on the edge, where MiNiFI runs, before sending semantic interpretations 
> upstream.
> Tensor Flow is a data flow system for processing tensors, and many graphs 
> exist or could be created which are well-suited to interpret signal inputs. 
> It would therefore be useful to have a processor in MiNiFi - C++ which takes 
> tensors (serialized as binary protocol buffers), feeds them into an input 
> node on a supplied graph, reads tensors from an output node, and finally 
> writes those output tensors as flow files containing binary protocol buffers.
> While there are many additional convenience utilities which would be helpful, 
> such as converting various standard sensor types into tensors, the initial 
> scope of this feature is a processor which processes arbitrary tensors 
> through arbitrary graphs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-296) Remove Flowfile reference count based on RAII

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-296.
--
Resolution: Won't Fix

Likely will not be able to do this, given the nature of flow and content 
management. 

> Remove Flowfile reference count based on RAII
> -
>
> Key: MINIFICPP-296
> URL: https://issues.apache.org/jira/browse/MINIFICPP-296
> Project: NiFi MiNiFi C++
>  Issue Type: Sub-task
>Reporter: marco polo
>Assignee: marco polo
>
> Remove Flowfile reference count based on RAII



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-45) consider moving away from std::queue

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-45.
-
Resolution: Won't Fix

> consider moving away from std::queue
> 
>
> Key: MINIFICPP-45
> URL: https://issues.apache.org/jira/browse/MINIFICPP-45
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: marco polo
>Assignee: marco polo
>Priority: Minor
>
> https://github.com/cameron314/concurrentqueue is a concurrent lock free queue 
> offering excellent performance with a palatable license. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-254) Connectable lock incorrect

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-254.
--
   Resolution: Fixed
Fix Version/s: 0.3.0

> Connectable lock incorrect
> --
>
> Key: MINIFICPP-254
> URL: https://issues.apache.org/jira/browse/MINIFICPP-254
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Fredrick Stakem
>Assignee: marco polo
>Priority: Minor
> Fix For: 0.3.0
>
>
> On class Connectable line 68 you define a lock required if it is running in 
> function isSupportedRelationship(). If the Connectable is running then 
> relationship_ does not change in the code. The relationship_ only can be 
> changed when the state is not running. Is this backwards?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-258) C2NullConfiguration fails due to a segfault on travis.

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-258:
-
Fix Version/s: 0.3.0

> C2NullConfiguration fails due to a segfault on travis. 
> ---
>
> Key: MINIFICPP-258
> URL: https://issues.apache.org/jira/browse/MINIFICPP-258
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-46) Convert StreamFactory to a controller service

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-46.
-
Resolution: Fixed

> Convert StreamFactory to a controller service
> -
>
> Key: MINIFICPP-46
> URL: https://issues.apache.org/jira/browse/MINIFICPP-46
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: marco polo
> Fix For: 0.3.0
>
>
> Once https://github.com/apache/nifi-minifi-cpp/pull/83/files is merged, we 
> can create more controller services. We can move the socket factory over to a 
> controller service which will allow us to better control socket 
> creation/reuse. Possibilities include limiting the number of sockets created, 
> what happens when that max is reached, more easily link services so that 
> secure sockets are created without the need for a static configuration in 
> minifi.properies



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-358) Implement TFExtractTopLabels

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-358:
-
Fix Version/s: 0.4.0

> Implement TFExtractTopLabels
> 
>
> Key: MINIFICPP-358
> URL: https://issues.apache.org/jira/browse/MINIFICPP-358
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
> Fix For: 0.4.0
>
>
> Add support for interpreting output tensors which represent labels with 
> scores. A list of labels in index order is passed in with attribute tf.type 
> == "labels". The top N labels are extracted into attributes tf.label. and 
> tf.score.. The tf.label.0 attribute represents the highest-scoring label 
> and can be used, for example, to route FlowFiles based on model inferences.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-222) PutFileTests compilation error in 'make docker'

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-222:
-
Fix Version/s: 0.3.0

> PutFileTests compilation error in 'make docker'
> ---
>
> Key: MINIFICPP-222
> URL: https://issues.apache.org/jira/browse/MINIFICPP-222
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
> Fix For: 0.3.0
>
>
> During build of docker container triggered by 'make docker:'
> {code}
> [ 75%] Building CXX object 
> CMakeFiles/PutFileTests.dir/libminifi/test/unit/PutFileTests.cpp.o
> In file included from 
> /opt/minifi/thirdparty/yaml-cpp-yaml-cpp-0.5.3/include/yaml-cpp/yaml.h:10:0,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/../../include/ConfigurationListener.h:30,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/../../include/FlowController.h:47,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/ProvenanceTestHelper.h:33,
>  from /opt/minifi/libminifi/test/unit/../TestBase.h:38,
>  from /opt/minifi/libminifi/test/unit/PutFileTests.cpp:28:
> /opt/minifi/thirdparty/yaml-cpp-yaml-cpp-0.5.3/include/yaml-cpp/parser.h:43:8:
>  warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>std::auto_ptr m_pScanner;
> ^~~~
> In file included from /usr/include/c++/6.4.0/memory:81:0,
>  from /opt/minifi/libminifi/test/unit/PutFileTests.cpp:22:
> /usr/include/c++/6.4.0/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> In file included from 
> /opt/minifi/thirdparty/yaml-cpp-yaml-cpp-0.5.3/include/yaml-cpp/yaml.h:10:0,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/../../include/ConfigurationListener.h:30,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/../../include/FlowController.h:47,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/ProvenanceTestHelper.h:33,
>  from /opt/minifi/libminifi/test/unit/../TestBase.h:38,
>  from /opt/minifi/libminifi/test/unit/PutFileTests.cpp:28:
> /opt/minifi/thirdparty/yaml-cpp-yaml-cpp-0.5.3/include/yaml-cpp/parser.h:44:8:
>  warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>std::auto_ptr m_pDirectives;
> ^~~~
> In file included from /usr/include/c++/6.4.0/memory:81:0,
>  from /opt/minifi/libminifi/test/unit/PutFileTests.cpp:22:
> /usr/include/c++/6.4.0/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> In file included from 
> /opt/minifi/thirdparty/yaml-cpp-yaml-cpp-0.5.3/include/yaml-cpp/yaml.h:11:0,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/../../include/ConfigurationListener.h:30,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/../../include/FlowController.h:47,
>  from 
> /opt/minifi/libminifi/test/unit/../unit/ProvenanceTestHelper.h:33,
>  from /opt/minifi/libminifi/test/unit/../TestBase.h:38,
>  from /opt/minifi/libminifi/test/unit/PutFileTests.cpp:28:
> /opt/minifi/thirdparty/yaml-cpp-yaml-cpp-0.5.3/include/yaml-cpp/emitter.h:125:8:
>  warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>std::auto_ptr m_pState;
> ^~~~
> In file included from /usr/include/c++/6.4.0/memory:81:0,
>  from /opt/minifi/libminifi/test/unit/PutFileTests.cpp:22:
> /usr/include/c++/6.4.0/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> /opt/minifi/libminifi/test/unit/PutFileTests.cpp: In function 'uint64_t 
> getModificationTime(std::__cxx11::string)':
> /opt/minifi/libminifi/test/unit/PutFileTests.cpp:52:19: error: 'struct stat' 
> has no member named 'st_mtimespec'; did you mean 'st_mtim'?
>  return result.st_mtimespec.tv_sec;
>^~~~
> make[2]: *** [CMakeFiles/PutFileTests.dir/build.make:63: 
> CMakeFiles/PutFileTests.dir/libminifi/test/unit/PutFileTests.cpp.o] Error 1
> make[1]: *** [CMakeFiles/Makefile2:876: CMakeFiles/PutFileTests.dir/all] 
> Error 2
> make: *** [Makefile:163: all] Error 2
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-46) Convert StreamFactory to a controller service

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-46:

Fix Version/s: 0.3.0

> Convert StreamFactory to a controller service
> -
>
> Key: MINIFICPP-46
> URL: https://issues.apache.org/jira/browse/MINIFICPP-46
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: marco polo
> Fix For: 0.3.0
>
>
> Once https://github.com/apache/nifi-minifi-cpp/pull/83/files is merged, we 
> can create more controller services. We can move the socket factory over to a 
> controller service which will allow us to better control socket 
> creation/reuse. Possibilities include limiting the number of sockets created, 
> what happens when that max is reached, more easily link services so that 
> secure sockets are created without the need for a static configuration in 
> minifi.properies



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-268) Implement ManipulateArchive processor

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-268:
-
Fix Version/s: 0.3.0

> Implement ManipulateArchive processor
> -
>
> Key: MINIFICPP-268
> URL: https://issues.apache.org/jira/browse/MINIFICPP-268
> Project: NiFi MiNiFi C++
>  Issue Type: New Feature
>Reporter: Caleb Johnson
> Fix For: 0.3.0
>
>
> The ManipulateArchive processor extends Un/FocusArchive by allowing users to 
> perform the following operations on archives supported by same:
> * Touch: create an empty file at the specified path;
> * Remove: repacks an archive, but skips the specified entry when rebuilding;
> * Move: rename an archive entry;
> * Copy: duplicate an archive entry to another path.
> Touch, move and copy operations take optional 'before' and 'after' parameters 
> to control where the modified entry is to be placed relative to an existing 
> one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFIREG-95) Help icon is displayed on the login page

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320986#comment-16320986
 ] 

ASF GitHub Bot commented on NIFIREG-95:
---

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/79


> Help icon is displayed on the login page
> 
>
> Key: NIFIREG-95
> URL: https://issues.apache.org/jira/browse/NIFIREG-95
> Project: NiFi Registry
>  Issue Type: Bug
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Trivial
> Fix For: 0.1.1
>
>
> The help icon is incorrectly displayed in the header toolbar when the user is 
> logging in.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-282) Improve test build speed and add Travis build cache

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-282:
-
Fix Version/s: 0.3.0

> Improve test build speed and add Travis build cache
> ---
>
> Key: MINIFICPP-282
> URL: https://issues.apache.org/jira/browse/MINIFICPP-282
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Caleb Johnson
>Priority: Minor
> Fix For: 0.3.0
>
>
> * Use Travis's caching feature to persist $HOME/.ccache
> * Enable parallel testing on Travis now that MINIFICPP-60 is merged
> * Build catch main() and spdlib as shared objects for all tests
>   * Best practices according to [catch 
> docs|https://github.com/philsquared/Catch/blob/master/docs/slow-compiles.md].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-261) Extensions not added to docker/minificppsource, causing make docker to fail

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-261:
-
Fix Version/s: 0.3.0

> Extensions not added to docker/minificppsource, causing make docker to fail
> ---
>
> Key: MINIFICPP-261
> URL: https://issues.apache.org/jira/browse/MINIFICPP-261
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
> Fix For: 0.3.0
>
>
> We're not adding the extensions/ dir to docker/minificppsource/, which 
> CMakeLists.txt references, so docker builds are failing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFIREG-95) Help icon is displayed on the login page

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320984#comment-16320984
 ] 

ASF GitHub Bot commented on NIFIREG-95:
---

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/79
  
Looks good, will merge


> Help icon is displayed on the login page
> 
>
> Key: NIFIREG-95
> URL: https://issues.apache.org/jira/browse/NIFIREG-95
> Project: NiFi Registry
>  Issue Type: Bug
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Trivial
> Fix For: 0.1.1
>
>
> The help icon is incorrectly displayed in the header toolbar when the user is 
> logging in.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-286) PutFile fails if filename property includes a path

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-286:
-
Fix Version/s: 0.3.0

> PutFile fails if filename property includes a path
> --
>
> Key: MINIFICPP-286
> URL: https://issues.apache.org/jira/browse/MINIFICPP-286
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
> Fix For: 0.3.0
>
>
> If a flowfile 'filename' property includes a path (i.e. nested subdirs), then 
> PutFile fails due to improper creation of temporary write file.
> Example ExecuteScript lua to update filename:
> {code}
> function onTrigger(context, session)
>   flow_file = session:get()
>   log:info('rename_file triggered')
>   if flow_file ~= nil then
> file_name = flow_file:getAttribute('filename')
> new_file_name = 'a/b/' .. file_name
> log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' .. 
> new_file_name)
> flow_file:updateAttribute('filename', new_file_name)
> session:transfer(flow_file, REL_SUCCESS)
> log:info('rename_file success')
>   else
> log:info('no work to do')
>   end
> end
> {code}
> Log output showing the error:
> {code}
> [2017-11-03 12:44:38.916] 
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available 
> lua script engine instance
> [2017-11-03 12:44:38.916] 
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file 
> triggered
> [2017-11-03 12:44:38.916] 
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming 
> 1509727478135549592 to a/b/1509727478135549592
> [2017-11-03 12:44:38.916] 
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file 
> success
> [2017-11-03 12:44:38.916] 
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua 
> script engine
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile] 
> [info] PutFile using temporary file 
> data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile] 
> [info] PutFile writing file a/b/1509727478135549592 into directory data
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile] 
> [info] Committing data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921] 
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile 
> committing put file operation to data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921] 
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile 
> commit put file operation to data/a/b/1509727478135549592 failed because 
> rename() call failed
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (NIFIREG-95) Help icon is displayed on the login page

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFIREG-95.

   Resolution: Fixed
Fix Version/s: 0.1.1

> Help icon is displayed on the login page
> 
>
> Key: NIFIREG-95
> URL: https://issues.apache.org/jira/browse/NIFIREG-95
> Project: NiFi Registry
>  Issue Type: Bug
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Trivial
> Fix For: 0.1.1
>
>
> The help icon is incorrectly displayed in the header toolbar when the user is 
> logging in.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-registry pull request #79: [NIFIREG-95] remove help icon button from he...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/79


---

[GitHub] nifi-registry issue #79: [NIFIREG-95] remove help icon button from header to...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/79
  
Looks good, will merge


---

[jira] [Assigned] (MINIFICPP-282) Improve test build speed and add Travis build cache

[marco polo (JIRA)]

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

marco polo reassigned MINIFICPP-282:


Assignee: Caleb Johnson

> Improve test build speed and add Travis build cache
> ---
>
> Key: MINIFICPP-282
> URL: https://issues.apache.org/jira/browse/MINIFICPP-282
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Caleb Johnson
>Assignee: Caleb Johnson
>Priority: Minor
> Fix For: 0.3.0
>
>
> * Use Travis's caching feature to persist $HOME/.ccache
> * Enable parallel testing on Travis now that MINIFICPP-60 is merged
> * Build catch main() and spdlib as shared objects for all tests
>   * Best practices according to [catch 
> docs|https://github.com/philsquared/Catch/blob/master/docs/slow-compiles.md].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-271) Unncessary Boost dependency in ProcessSession.h

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-271:
-
Fix Version/s: 0.3.0

> Unncessary Boost dependency in ProcessSession.h
> ---
>
> Key: MINIFICPP-271
> URL: https://issues.apache.org/jira/browse/MINIFICPP-271
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Dustin Rodrigues
> Fix For: 0.3.0
>
>
> There's an unnecessary header file included for Boost in ProcessSession.h 
> causing build errors on OSX.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFIREG-94) Clean up WARNINGs when building Registry Docs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321026#comment-16321026
 ] 

ASF GitHub Bot commented on NIFIREG-94:
---

Github user kevdoran commented on the issue:

https://github.com/apache/nifi-registry/pull/76
  
+1, nice work @andrewmlim. going to merge to master


> Clean up WARNINGs when building Registry Docs
> -
>
> Key: NIFIREG-94
> URL: https://issues.apache.org/jira/browse/NIFIREG-94
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Trivial
>
> Noticed when building docs, the user guide has the following WARNINGs:
> asciidoctor: WARNING: user-guide.adoc: line 91: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 123: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 133: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 144: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 159: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 165: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 172: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 178: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 182: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 188: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 193: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 198: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 204: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 208: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 231: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 236: list item index: expected 1, 
> got 4
> asciidoctor: WARNING: user-guide.adoc: line 248: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 257: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 273: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 279: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 285: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 291: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 295: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 301: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 306: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 311: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 317: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 325: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 342: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 347: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 352: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 358: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 365: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 373: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 378: list item index: expected 1, 
> got 4
> asciidoctor: WARNING: user-guide.adoc: line 384: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 390: list item index: expected 1, 
> got 2
> asciidoctor: WARNING: user-guide.adoc: line 395: list item index: expected 1, 
> got 3
> asciidoctor: WARNING: user-guide.adoc: line 399: section title out of 
> sequence: expected level 2, got level 3
> asciidoctor: WARNING: user-guide.adoc: line 416: section title out of 
> sequence: expected level 2, got level 3



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFIREG-99) Add a refresh icon button to the 'Change Log' for an item

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320876#comment-16320876
 ] 

ASF GitHub Bot commented on NIFIREG-99:
---

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/80


> Add a refresh icon button to the 'Change Log' for an item
> -
>
> Key: NIFIREG-99
> URL: https://issues.apache.org/jira/browse/NIFIREG-99
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Minor
>
> As a user I want to be able to refresh the item's details without refreshing 
> the whole page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-registry pull request #80: [NIFIREG-99] add refresh button to an items ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/80


---

[jira] [Commented] (NIFIREG-99) Add a refresh icon button to the 'Change Log' for an item

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320873#comment-16320873
 ] 

ASF GitHub Bot commented on NIFIREG-99:
---

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/80
  
Looks good, will merge


> Add a refresh icon button to the 'Change Log' for an item
> -
>
> Key: NIFIREG-99
> URL: https://issues.apache.org/jira/browse/NIFIREG-99
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Minor
>
> As a user I want to be able to refresh the item's details without refreshing 
> the whole page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #235: MINIFICPP-364: resolve issues with test e...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/235


---

[GitHub] nifi-minifi-cpp issue #37: MINIFI-171 Dynamic Properties support for process...

[achristianson]

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/37
  
Taking this on.


---

[jira] [Commented] (MINIFICPP-358) Implement TFExtractTopLabels

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320892#comment-16320892
 ] 

ASF GitHub Bot commented on MINIFICPP-358:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/232


> Implement TFExtractTopLabels
> 
>
> Key: MINIFICPP-358
> URL: https://issues.apache.org/jira/browse/MINIFICPP-358
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>
> Add support for interpreting output tensors which represent labels with 
> scores. A list of labels in index order is passed in with attribute tf.type 
> == "labels". The top N labels are extracted into attributes tf.label. and 
> tf.score.. The tf.label.0 attribute represents the highest-scoring label 
> and can be used, for example, to route FlowFiles based on model inferences.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (NIFI-4753) Add Get Kudu Processor

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-4753:
-

Assignee: Matt Gilman

> Add Get Kudu Processor
> --
>
> Key: NIFI-4753
> URL: https://issues.apache.org/jira/browse/NIFI-4753
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Sri Sai Kumar Ravipati
>Assignee: Matt Gilman
>
> Now that we have the Put Kudu processor service currently in master, it would 
> be nice to have Get Kudu processor as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MINIFICPP-118) Dynamic Properties support for processors

[Andrew Christianson (JIRA)]

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

Andrew Christianson reassigned MINIFICPP-118:
-

Assignee: Andrew Christianson  (was: Jeremy Dyer)

> Dynamic Properties support for processors
> -
>
> Key: MINIFICPP-118
> URL: https://issues.apache.org/jira/browse/MINIFICPP-118
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Jeremy Dyer
>Assignee: Andrew Christianson
>
> Currently any Property read from the config.yml file that is not explicitly 
> defined in the processor's implementation will be ignored by Processor.cpp 
> when reading the configurations. This prevents any dynamic property from 
> being defined in the config.yml and passed to the processor at runtime. 
> Certain processors rely heavily on the concept of dynamic properties that are 
> passed to them at runtime to handle things like setting dynamic properties 
> based on properties that are declared. All of these possibilities cannot be 
> handled upfront so there should be a mechanism, most likely in Processor.cpp, 
> that allows for a list of dynamicProperties that are parsed form the 
> config.yml file to be stored and accessed by the underlying processor 
> implementation at runtime and use them as the processor desires.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (NIFI-4753) Add Get Kudu Processor

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-4753:
-

Assignee: (was: Matt Gilman)

> Add Get Kudu Processor
> --
>
> Key: NIFI-4753
> URL: https://issues.apache.org/jira/browse/NIFI-4753
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Sri Sai Kumar Ravipati
>
> Now that we have the Put Kudu processor service currently in master, it would 
> be nice to have Get Kudu processor as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MINIFICPP-370) Implement type coercion in expression language

[Andrew Christianson (JIRA)]

Andrew Christianson created MINIFICPP-370:
-

 Summary: Implement type coercion in expression language
 Key: MINIFICPP-370
 URL: https://issues.apache.org/jira/browse/MINIFICPP-370
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Andrew Christianson


Type Coercion
toString
toNumber
toDecimal



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-350) Fix compilation warnings

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated MINIFICPP-350:
--
Fix Version/s: 0.4.0

> Fix compilation warnings
> 
>
> Key: MINIFICPP-350
> URL: https://issues.apache.org/jira/browse/MINIFICPP-350
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Dustin Rodrigues
>Priority: Minor
> Fix For: 0.4.0
>
>
> Fix compilation warnings in PutFile and Expression



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-350) Fix compilation warnings

[Aldrin Piri (JIRA)]

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

Aldrin Piri resolved MINIFICPP-350.
---
Resolution: Fixed

> Fix compilation warnings
> 
>
> Key: MINIFICPP-350
> URL: https://issues.apache.org/jira/browse/MINIFICPP-350
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Dustin Rodrigues
>Priority: Minor
> Fix For: 0.4.0
>
>
> Fix compilation warnings in PutFile and Expression



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-352) verify and resolve issues with bootstrap on RPI

[marco polo (JIRA)]

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

marco polo resolved MINIFICPP-352.
--
Resolution: Fixed

> verify and resolve issues with bootstrap on RPI
> ---
>
> Key: MINIFICPP-352
> URL: https://issues.apache.org/jira/browse/MINIFICPP-352
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-280) Move extension tests and test headers, lint extensions

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-280:
-
Fix Version/s: 0.3.0

> Move extension tests and test headers, lint extensions
> --
>
> Key: MINIFICPP-280
> URL: https://issues.apache.org/jira/browse/MINIFICPP-280
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Caleb Johnson
>Priority: Minor
> Fix For: 0.3.0
>
>
> * move extension tests into their respective folders
> * separate source and header files
> * remove unnecessary or nonexisting include directories
> * run linter on extension source files as part of linter target
> * clean up extensions according to linter
> * add ability to specify more than one include and source folder for linter



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-270) Simplify creation of extensions

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-270:
-
Fix Version/s: 0.3.0

> Simplify creation of extensions
> ---
>
> Key: MINIFICPP-270
> URL: https://issues.apache.org/jira/browse/MINIFICPP-270
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>
> Creating an extension requires copy/paste of a several blocks. We should 
> create functions that simplify the creation of extensions.
> At a minimum we need the extension name, a description, and test directory 
> for a function. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-236) Consider moving to Boost ASIO to minimize platform specific socket code.

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-236:
-
Fix Version/s: 0.2.0

> Consider moving to Boost ASIO to minimize platform specific socket code. 
> -
>
> Key: MINIFICPP-236
> URL: https://issues.apache.org/jira/browse/MINIFICPP-236
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.2.0
>
>
> Boost ASIO can be built separately and doesn't require boost libs/headers, 
> minimizing the size. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-293) Insufficient space in atomic entry error, after running for a while

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-293:
-
Fix Version/s: 0.3.0

> Insufficient space in atomic entry error, after running for a while
> ---
>
> Key: MINIFICPP-293
> URL: https://issues.apache.org/jira/browse/MINIFICPP-293
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: marco polo
> Fix For: 0.3.0
>
> Attachments: example.tar.xz, logs.tar.xz
>
>
> I have a flow that looks like this:
> {code}
> # Licensed to the Apache Software Foundation (ASF) under one or more
> # contributor license agreements.  See the NOTICE file distributed with
> # this work for additional information regarding copyright ownership.
> # The ASF licenses this file to You under the Apache License, Version 2.0
> # (the \"License\"); you may not use this file except in compliance with
> # the License.  You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an \"AS IS\" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
> Flow Controller:
>   name: MiNiFi Flow
> Processors:
>   - name: GetFeedURLs
> class: org.apache.nifi.processors.standard.GetFile
> scheduling strategy: TIMER_DRIVEN
> max concurrent tasks: 1
> scheduling period: 1 sec
> #scheduling period: 100 ms
> auto-terminated relationships list:
>   - failure
> Properties:
>   Input Directory: data/rss/feeds
>   Keep Source File: true
>   #File Filter: "/url$"
>   - name: ExtractURL
> class: org.apache.nifi.processors.standard.ExtractText
> auto-terminated relationships list:
>   - failure
> Properties:
>   Attribute: feed_url
>   - name: PaceFetch
> class: org.apache.nifi.processors.standard.ExecuteScript
> auto-terminated relationships list:
>   - failure
> Properties:
>   Script Engine: lua
>   Script File: conf/PaceFetch.lua
>   - name: FetchFeed
> class: org.apache.nifi.processors.standard.ExecuteScript
> max concurrent tasks: 5
> auto-terminated relationships list:
>   - failure
> Properties:
>   Script Engine: python
>   Script File: conf/ExecA.py
>   - name: LogEntryAttributes
> class: org.apache.nifi.processors.standard.LogAttribute
> auto-terminated relationships list:
>   - failure
>   - name: PutEntry
> class: org.apache.nifi.processors.standard.PutFile
> auto-terminated relationships list:
>   - success
>   - failure
> Properties:
>   Directory: data
>   Conflict Resolution Strategy: ignore
> Connections:
>   - name: A
> source name: GetFeedURLs
> source relationship name: success
> destination name: ExtractURL
>   - name: B
> source name: ExtractURL
> source relationship name: success
> destination name: PaceFetch
>   - name: C
> source name: PaceFetch
> source relationship name: success
> destination name: FetchFeed
>   - name: D
> source name: FetchFeed
> source relationship name: success
> destination name: LogEntryAttributes
>   - name: E
> source name: LogEntryAttributes
> source relationship name: success
> destination name: PutEntry
> Remote Processing Groups: []
> Provenance Reporting:
> {code}
> After it runs for a while (hour or two), the flow stops fully working, and 
> dumps this out in the DEBUG logs:
> {code}
> [2017-11-06 11:37:57.063] [org::apache::nifi::minifi::core::ProcessSession] 
> [debug] Create FlowFile with UUID d81b1832-c310-11e7-a858-bc5ff43a885b
> [2017-11-06 11:37:57.063] 
> [org::apache::nifi::minifi::provenance::ProvenanceReporter] [debug] Prove 
> reporter now 3
> [2017-11-06 11:37:57.063] [org::apache::nifi::minifi::ResourceClaim] [debug] 
> Resource Claim created ./content_repository/1509982623798-8558
> [2017-11-06 11:37:57.063] 
> [org::apache::nifi::minifi::core::repository::VolatileContentRepository] 
> [debug] enter write for ./content_repository/1509982623798-8558
> [2017-11-06 11:37:57.063] 
> [org::apache::nifi::minifi::core::repository::VolatileContentRepository] 
> [debug] Minimize locking
> [2017-11-06 11:37:57.064] 
> [org::apache::nifi::minifi::io::AtomicEntryStream  > ()] [debug] Cannot insert 46 bytes due to insufficient space in atomic 
> entry
> [2017-11-06 11:37:57.064] 
> [org::apache::nifi::minifi::io::AtomicEntryStream  > ()] [debug] Decrementing
> [2017-11-06 11:37:57.064] 

[jira] [Updated] (MINIFICPP-239) Clean up test directory to separate integration from unit tests.

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-239:
-
Fix Version/s: (was: 0.3.0)
   0.2.0

> Clean up test directory to separate integration from unit tests.
> 
>
> Key: MINIFICPP-239
> URL: https://issues.apache.org/jira/browse/MINIFICPP-239
> Project: NiFi MiNiFi C++
>  Issue Type: Test
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.2.0
>
>
> Recent changes have moved integration tests into the root of /test/ while 
> unit tests are in /tests/unit/ . We should clean this up and potentially add 
> targets to separate these. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-253) ContentRepository should remove items from count_map_.

[Aldrin Piri (JIRA)]

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

Aldrin Piri resolved MINIFICPP-253.
---
Resolution: Fixed

> ContentRepository should remove items from count_map_. 
> ---
>
> Key: MINIFICPP-253
> URL: https://issues.apache.org/jira/browse/MINIFICPP-253
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>
> removeIfOrphaned in ContentRepository should remove the key/value pair from 
> count_map_. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MINIFICPP-267) MiNiFiMain crashes and fails to infer MINIFI_HOME if MINIFI_HOME not set

[marco polo (JIRA)]

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

marco polo updated MINIFICPP-267:
-
Fix Version/s: 0.3.0

> MiNiFiMain crashes and fails to infer MINIFI_HOME if MINIFI_HOME not set
> 
>
> Key: MINIFICPP-267
> URL: https://issues.apache.org/jira/browse/MINIFICPP-267
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Minor
> Fix For: 0.3.0
>
>
> When launching minifi cmd direcly without setting MINIFI_HOME, minifi tries 
> to infer MINIFI_HOME based on the exe path. This crashes the minifi (CentOS 
> 7.4).
> {code}
> [main] [info] MINIFI_HOME was not found, determining based on executable path.
> terminate called after throwing an instance of 'std::logic_error'
>   what():  basic_string::_S_construct null not valid
> Aborted (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFIREG-110) Add when viewing flows

[Andrew Lim (JIRA)]

Andrew Lim created NIFIREG-110:
--

 Summary: Add when viewing flows
 Key: NIFIREG-110
 URL: https://issues.apache.org/jira/browse/NIFIREG-110
 Project: NiFi Registry
  Issue Type: Improvement
Affects Versions: 0.1.0
Reporter: Andrew Lim
Priority: Minor


It would be helpful if the UI showed the number of flows.

This would also be consistent with how the number of buckets and users are 
displayed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)