[jira] [Moved] (MINIFICPP-1341) no matching conversion for static_cast from 'const org::apache::nifi::minifi::core::PropertyValue' to 'std::__1::chrono::duration >'
[ https://issues.apache.org/jira/browse/MINIFICPP-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri moved MINIFI-535 to MINIFICPP-1341: --- Component/s: (was: Build) Key: MINIFICPP-1341 (was: MINIFI-535) Affects Version/s: (was: 1.0.0) 1.0.0 Project: Apache NiFi MiNiFi C++ (was: Apache NiFi MiNiFi) > no matching conversion for static_cast from 'const > org::apache::nifi::minifi::core::PropertyValue' to > 'std::__1::chrono::duration >' > > > Key: MINIFICPP-1341 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1341 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Affects Versions: 1.0.0 > Environment: $ cmake --version > cmake version 3.16.3 > $ clang --version > clang version 10.0.0-4ubuntu1 > Target: x86_64-pc-linux-gnu > Thread model: posix >Reporter: Ivan Serdyuk >Priority: Critical > Labels: clang > Attachments: TailFile_build_error.log > > > I was compiling MiNiFi using Clang 10.0.0-4ubuntu1 release. > I did like this: > $ cmake -DENABLE_COAP=ON -DASAN_BUILD=ON -DSKIP_TESTS=ON -DUSE_SHARED_LIBS=ON > -DPORTABLE=ON -DBUILD_ROCKSDB=ON -DBUILD_IDENTIFIER= > -DCMAKE_BUILD_TYPE=MinSizeRel -DFAIL_ON_WARNINGS= -DCMAKE_C_COMPILER=clang > -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS="-stdlib=libc++" .. > And (eventually) got this: > [ 47%] Building CXX object > extensions/standard-processors/CMakeFiles/minifi-standard-processors.dir/processors/TailFile.cpp.o > In file included from > /home/ubuntu/minifi_cpp/extensions/standard-processors/processors/TailFile.cpp:40: > In file included from > /home/ubuntu/minifi_cpp/extensions/standard-processors/processors/TailFile.h:30: > In file included from > /home/ubuntu/minifi_cpp/extensions/standard-processors/../../libminifi/include/core/Processor.h:39: > /home/ubuntu/minifi_cpp/extensions/standard-processors/../../libminifi/include/core/ConfigurableComponent.h:230:13: > error: no matching conversion for static_cast from 'const > org::apache::nifi::minifi::core::PropertyValue' to > 'std::__1::chrono::duration >' > value = static_cast(item.getValue()); > ^~~ > /home/ubuntu/minifi_cpp/extensions/standard-processors/../../libminifi/include/core/ProcessorNode.h:71:30: > note: in instantiation of function template specialization > 'org::apache::nifi::minifi::core::ConfigurableComponent::getProperty long, std::__1::ratio<1, 1000> > >' requested here > return processor_cast->getProperty(name, value); > ^ > /home/ubuntu/minifi_cpp/extensions/standard-processors/../../libminifi/include/core/ProcessContext.h:329:29: > note: in instantiation of function template specialization > 'org::apache::nifi::minifi::core::ProcessorNode::getProperty long, std::__1::ratio<1, 1000> > >' requested here > return processor_node_->getProperty std::common_type::type>(name, value); > ^ > /home/ubuntu/minifi_cpp/extensions/standard-processors/../../libminifi/include/core/ProcessContext.h:102:12: > note: in instantiation of function template specialization > 'org::apache::nifi::minifi::core::ProcessContext::getPropertyImp long, std::__1::ratio<1, 1000> > >' requested here > return getPropertyImp::type>(name, value); > ^ > /home/ubuntu/minifi_cpp/extensions/standard-processors/processors/TailFile.cpp:367:14: > note: in instantiation of function template specialization > 'org::apache::nifi::minifi::core::ProcessContext::getProperty long, std::__1::ratio<1, 1000> > >' requested here > context->getProperty(LookupFrequency.getName(), lookup_frequency_); > ^ > /usr/lib/llvm-10/bin/../include/c++/v1/chrono:1021:28: note: candidate > constructor (the implicit copy constructor) not viable: no known conversion > from 'const org::apache::nifi::minifi::core::PropertyValue' to 'const > std::__1::chrono::duration >' for 1st > argument > class _LIBCPP_TEMPLATE_VIS duration > ^ > /usr/lib/llvm-10/bin/../include/c++/v1/chrono:1021:28: note: candidate > constructor (the implicit move constructor) not viable: no known conversion > from 'const org::apache::nifi::minifi::core::PropertyValue' to > 'std::__1::chrono::duration >' for 1st > argument > /usr/lib/llvm-10/bin/../include/c++/v1/chrono:1073:18: note: candidate > template ignored: requirement > 'is_convertible long>::value' was not satisfied [with _Rep2 = > org::apache::nifi::minifi::core::PropertyValue] > explicit duration(const _Rep2& __r, > ^ > /usr/lib/llvm-10/bin/../include/c++/v1/chrono:1085:9: note: candidate > template ignored: could not match 'duration type-parameter-0-1>' against 'const >
[jira] [Resolved] (NIFIREG-389) libnpx not found
[ https://issues.apache.org/jira/browse/NIFIREG-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFIREG-389. - Resolution: Fixed > libnpx not found > > > Key: NIFIREG-389 > URL: https://issues.apache.org/jira/browse/NIFIREG-389 > Project: NiFi Registry > Issue Type: Bug >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 1.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Users who do not have npx installed globally can run into a build issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFIREG-391) Master (2881e2) currently failing on tests
[ https://issues.apache.org/jira/browse/NIFIREG-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111571#comment-17111571 ] Aldrin Piri commented on NIFIREG-391: - Did not dig into the specific tests, but at a cursory glance appears it may be timestamp related. This was done on an Ubuntu based system. $ mvn -version Apache Maven 3.6.3 Maven home: /usr/share/maven Java version: 1.8.0_252, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.4.0-29-generic", arch: "amd64", family: "unix" > Master (2881e2) currently failing on tests > -- > > Key: NIFIREG-391 > URL: https://issues.apache.org/jira/browse/NIFIREG-391 > Project: NiFi Registry > Issue Type: Bug >Reporter: Aldrin Piri >Priority: Major > > Master (hash: 2881e29dce3a179f3e56069b82ef8cbb7bd8d85c) is currently failing > on ITs. > Failed tests: > BucketsIT.testCreateBucketGetBucket:148 expected:<1589924875387> but > was:<1589910475387> > BucketsIT.testDeleteBucket:268 expected:<1589924875360> but > was:<1589910475360> > BucketsIT.testUpdateBucket:199 expected:<1589924875324> but > was:<1589910475324> > FlowsIT.testCreateFlowGetFlow:157 expected:<1589924880021> but > was:<1589910480021> > FlowsIT.testCreateFlowVersionGetFlowVersion:466 expected:<1589924880090> > but was:<1589910480090> > FlowsIT.testDeleteFlow:292 expected:<1589924880124> but was:<1589910480124> > FlowsIT.testUpdateFlow:217 expected:<1589924879924> but was:<1589910479924> -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFIREG-391) Master (2881e2) currently failing on tests
Aldrin Piri created NIFIREG-391: --- Summary: Master (2881e2) currently failing on tests Key: NIFIREG-391 URL: https://issues.apache.org/jira/browse/NIFIREG-391 Project: NiFi Registry Issue Type: Bug Reporter: Aldrin Piri Master (hash: 2881e29dce3a179f3e56069b82ef8cbb7bd8d85c) is currently failing on ITs. Failed tests: BucketsIT.testCreateBucketGetBucket:148 expected:<1589924875387> but was:<1589910475387> BucketsIT.testDeleteBucket:268 expected:<1589924875360> but was:<1589910475360> BucketsIT.testUpdateBucket:199 expected:<1589924875324> but was:<1589910475324> FlowsIT.testCreateFlowGetFlow:157 expected:<1589924880021> but was:<1589910480021> FlowsIT.testCreateFlowVersionGetFlowVersion:466 expected:<1589924880090> but was:<1589910480090> FlowsIT.testDeleteFlow:292 expected:<1589924880124> but was:<1589910480124> FlowsIT.testUpdateFlow:217 expected:<1589924879924> but was:<1589910479924> -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1194) MiNiFi-DOCS - Fix Table Formatting for 2 Execute.* Processors
[ https://issues.apache.org/jira/browse/MINIFICPP-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1194: --- Fix Version/s: 0.8.0 > MiNiFi-DOCS - Fix Table Formatting for 2 Execute.* Processors > - > > Key: MINIFICPP-1194 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1194 > Project: Apache NiFi MiNiFi C++ > Issue Type: Documentation >Affects Versions: master > Environment: Ubuntu 18.04 LTS in AWS EC2 >Reporter: James Medel >Priority: Major > Fix For: 0.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Table formatting issues were making it difficult to read properties for > ExecutePythonProcessor and ExecuteScript. So, this change in markdown > resolves the formatting issues. > Doc affected: > [https://github.com/apache/nifi-minifi-cpp/blob/master/PROCESSORS.md#executescript] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1195) MiNiFiCPP-DOCS: Updates README Outdated Bootstrapping Info
[ https://issues.apache.org/jira/browse/MINIFICPP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1195: --- Fix Version/s: (was: master) 0.8.0 > MiNiFiCPP-DOCS: Updates README Outdated Bootstrapping Info > -- > > Key: MINIFICPP-1195 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1195 > Project: Apache NiFi MiNiFi C++ > Issue Type: Documentation >Affects Versions: master > Environment: Ubuntu 18.04 LTS on AWS EC2 >Reporter: James Medel >Priority: Major > Fix For: 0.8.0 > > > The paragraph in the Getting Started: Bootstrapping section originally told > the user to enter N to continue the build process, but with the updated menu > guided bootstrap process displayed in the console, P is what one must enter > to continue the build process. I updated that info. > The previous menu guided bootstrap process was outdated and did not show the > new features Bustache Support to SQL Support and the Build Options. So, I > updated it to show that information. > > Here is my pull request with the updates: > [https://github.com/apache/nifi-minifi-cpp/pull/760] > Here is the doc that I am proposing updates for: > [https://github.com/apache/nifi-minifi-cpp/blob/master/README.md] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7354) Allow dynamic configuration of analytics properties in Docker
[ https://issues.apache.org/jira/browse/NIFI-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-7354: -- Fix Version/s: 1.12.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Allow dynamic configuration of analytics properties in Docker > - > > Key: NIFI-7354 > URL: https://issues.apache.org/jira/browse/NIFI-7354 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.12.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Until NIFI-6232 is implemented, it would be nice to be able to specify the > analytics properties via environment variables as is done for other > properties. Here are the defaults: > nifi.analytics.predict.enabled=false > nifi.analytics.predict.interval=3 mins > nifi.analytics.query.interval=5 mins > nifi.analytics.connection.model.implementation=org.apache.nifi.controller.status.analytics.models.OrdinaryLeastSquares > nifi.analytics.connection.model.score.name=rSquared > nifi.analytics.connection.model.score.threshold=.90 > At the least it would be good to be able to enable the analytics capability > this way, but might as well do all of them at once. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-7088) Provide tooling to publish release images to Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-7088. --- Resolution: Fixed > Provide tooling to publish release images to Docker Hub > --- > > Key: NIFI-7088 > URL: https://issues.apache.org/jira/browse/NIFI-7088 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker, Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > We have a series of Docker images that we release. This is typically a > manual process with the same set of commands. These should be translated > into script/Makefile to support performing these operations a bit more > consistently and easily. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7088) Provide tooling to publish release images to Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-7088: -- Priority: Minor (was: Major) > Provide tooling to publish release images to Docker Hub > --- > > Key: NIFI-7088 > URL: https://issues.apache.org/jira/browse/NIFI-7088 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker, Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > We have a series of Docker images that we release. This is typically a > manual process with the same set of commands. These should be translated > into script/Makefile to support performing these operations a bit more > consistently and easily. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7088) Provide tooling to publish release images to Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064471#comment-17064471 ] Aldrin Piri commented on NIFI-7088: --- Don't believe this needs to be incorporated into the NiFi source, but I have done a straightforward, brute-force script to perform these steps, available at [https://gist.github.com/apiri/1e9e38d485e18273bf97bc96f4885b76.] If there is a desire to get this into a community repo, happy to help that process. > Provide tooling to publish release images to Docker Hub > --- > > Key: NIFI-7088 > URL: https://issues.apache.org/jira/browse/NIFI-7088 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker, Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > > We have a series of Docker images that we release. This is typically a > manual process with the same set of commands. These should be translated > into script/Makefile to support performing these operations a bit more > consistently and easily. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (NIFI-7088) Provide tooling to publish release images to Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064471#comment-17064471 ] Aldrin Piri edited comment on NIFI-7088 at 3/23/20, 1:26 AM: - Don't believe this needs to be incorporated into the NiFi source, but I have done a straightforward, brute-force script to perform these steps, available at [https://gist.github.com/apiri/1e9e38d485e18273bf97bc96f4885b76]. If there is a desire to get this into a community repo, happy to help that process. was (Author: aldrin): Don't believe this needs to be incorporated into the NiFi source, but I have done a straightforward, brute-force script to perform these steps, available at [https://gist.github.com/apiri/1e9e38d485e18273bf97bc96f4885b76.] If there is a desire to get this into a community repo, happy to help that process. > Provide tooling to publish release images to Docker Hub > --- > > Key: NIFI-7088 > URL: https://issues.apache.org/jira/browse/NIFI-7088 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker, Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > > We have a series of Docker images that we release. This is typically a > manual process with the same set of commands. These should be translated > into script/Makefile to support performing these operations a bit more > consistently and easily. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1171) Fix "%ll" format strings in log lines
[
https://issues.apache.org/jira/browse/MINIFICPP-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri resolved MINIFICPP-1171.
Resolution: Fixed
> Fix "%ll" format strings in log lines
> -
>
> Key: MINIFICPP-1171
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1171
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Arpad Boda
>Assignee: Arpad Boda
>Priority: Minor
> Fix For: 0.8.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> Malformed log strings don't print the value.
> As an example, this line of code:
> {code}./extensions/civetweb/processors/ListenHTTP.cpp:287:
> logger_->log_debug("ListenHTTP handling POST request of length %ll",
> req_info->content_length);{code}
> Results in the following log message:
> {code}[2020-03-03 17:00:29.710]
> [org::apache::nifi::minifi::processors::ListenHTTP::Handler] [debug]
> ListenHTTP handling POST request of length{code}
> (Compiled with g++8.3 on Debian Buster)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MINIFICPP-952) Make Travis builds faster
[ https://issues.apache.org/jira/browse/MINIFICPP-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045712#comment-17045712 ] Aldrin Piri commented on MINIFICPP-952: --- Given the success NiFi has had with their switch, it may behoove us to also use GitHub actions. > Make Travis builds faster > - > > Key: MINIFICPP-952 > URL: https://issues.apache.org/jira/browse/MINIFICPP-952 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Dániel Bakai >Priority: Major > > * More and more often multiple builds time out > * Find out if there is a trivial fix (we include large template headers > where they are not needed, etc.) > * Moving hpps to cpps might help > * Improve caching -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6809) Update README to make use of ASF url for community slack channel
[ https://issues.apache.org/jira/browse/NIFI-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-6809: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Update README to make use of ASF url for community slack channel > > > Key: NIFI-6809 > URL: https://issues.apache.org/jira/browse/NIFI-6809 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Trivial > Time Spent: 50m > Remaining Estimate: 0h > > We can use the shortened URL https://s.apache.org/nifi-community-slack to > point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7116) Update Homebrew formula to handle state between version upgrades
[ https://issues.apache.org/jira/browse/NIFI-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-7116: -- Description: Currently, every NiFi upgrade in Homebrew causes all state to be lost and users must start over or manually migrate their repos and flow. We should improve the homebrew formula to include files that will persist between versions and default to properties that preserve this. Homebrew's guidance on the subject can be found at https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md#handling-files-that-should-persist-over-formula-upgrades. Formula: https://github.com/Homebrew/homebrew-core/blob/master/Formula/nifi.rb was: Currently, every NiFi upgrade in Homebrew causes all state to be lost and users must start over or manually migrate their repos and flow. We should improve the homebrew formula to include files that will persist between versions and default to properties that preserve this. Homebrew's guidance on the subject can be found at https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md#handling-files-that-should-persist-over-formula-upgrades. > Update Homebrew formula to handle state between version upgrades > > > Key: NIFI-7116 > URL: https://issues.apache.org/jira/browse/NIFI-7116 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Aldrin Piri >Priority: Minor > > Currently, every NiFi upgrade in Homebrew causes all state to be lost and > users must start over or manually migrate their repos and flow. > We should improve the homebrew formula to include files that will persist > between versions and default to properties that preserve this. Homebrew's > guidance on the subject can be found at > https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md#handling-files-that-should-persist-over-formula-upgrades. > Formula: https://github.com/Homebrew/homebrew-core/blob/master/Formula/nifi.rb -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7116) Update Homebrew formula to handle state between version upgrades
Aldrin Piri created NIFI-7116: - Summary: Update Homebrew formula to handle state between version upgrades Key: NIFI-7116 URL: https://issues.apache.org/jira/browse/NIFI-7116 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: Aldrin Piri Currently, every NiFi upgrade in Homebrew causes all state to be lost and users must start over or manually migrate their repos and flow. We should improve the homebrew formula to include files that will persist between versions and default to properties that preserve this. Homebrew's guidance on the subject can be found at https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md#handling-files-that-should-persist-over-formula-upgrades. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7088) Provide tooling to publish release images to Docker Hub
Aldrin Piri created NIFI-7088: - Summary: Provide tooling to publish release images to Docker Hub Key: NIFI-7088 URL: https://issues.apache.org/jira/browse/NIFI-7088 Project: Apache NiFi Issue Type: Improvement Components: Docker, Tools and Build Reporter: Aldrin Piri Assignee: Aldrin Piri We have a series of Docker images that we release. This is typically a manual process with the same set of commands. These should be translated into script/Makefile to support performing these operations a bit more consistently and easily. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027048#comment-17027048 ] Aldrin Piri commented on NIFI-7080: --- [~Absolutesantaja] Certainly. By migrating the check to the Dockerfile we ensure a consistent environment to hopefully eradicate those differences and address them in one place. > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 1.11.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027037#comment-17027037 ] Aldrin Piri commented on NIFI-7080: --- [~Absolutesantaja] Didn't see that one however I don't have confidence that actually solves the problem described by Kevin. I suspect that the plugin(s) used to zip up the source artifact lose permissions of the zip file, and as a result, can leave things in the state where we are unable to run. While changing the permissions _should_ be sufficient, this ticket and approach ensures they will be correct. > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 1.11.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027037#comment-17027037 ] Aldrin Piri edited comment on NIFI-7080 at 1/30/20 10:06 PM: - [~Absolutesantaja] Didn't see that one however I don't have confidence that actually solves the problem described by Kevin. I suspect that the plugin(s) used to zip up the source artifact lose permissions when creating the zip file, and as a result, can leave things in the state where we are unable to run. While changing the permissions _should_ be sufficient, this ticket and approach ensures they will be correct. was (Author: aldrin): [~Absolutesantaja] Didn't see that one however I don't have confidence that actually solves the problem described by Kevin. I suspect that the plugin(s) used to zip up the source artifact lose permissions of the zip file, and as a result, can leave things in the state where we are unable to run. While changing the permissions _should_ be sufficient, this ticket and approach ensures they will be correct. > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 1.11.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026986#comment-17026986 ] Aldrin Piri commented on NIFI-7080: --- Hey [~kdoran], Fixed this up. Would be great if we could land it in time for the next RC. > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 1.11.1 > > Time Spent: 10m > Remaining Estimate: 0h > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-7080: -- Status: Patch Available (was: In Progress) > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-7080: -- Fix Version/s: 1.11.1 > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 1.11.1 > > Time Spent: 10m > Remaining Estimate: 0h > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7080) Building from source release leads to non-functioning docker image
[ https://issues.apache.org/jira/browse/NIFI-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-7080: -- Priority: Minor (was: Major) > Building from source release leads to non-functioning docker image > -- > > Key: NIFI-7080 > URL: https://issues.apache.org/jira/browse/NIFI-7080 > Project: Apache NiFi > Issue Type: Bug > Components: Docker, Tools and Build >Affects Versions: 1.11.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > From the 1.11 release vote [~kdoran] reported an issue with the Docker build > working via Maven. > (https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). > This is the result of our zip source which does not preserve permissions and > makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7080) Building from source release leads to non-functioning docker image
Aldrin Piri created NIFI-7080: - Summary: Building from source release leads to non-functioning docker image Key: NIFI-7080 URL: https://issues.apache.org/jira/browse/NIFI-7080 Project: Apache NiFi Issue Type: Bug Components: Docker, Tools and Build Affects Versions: 1.11.0 Reporter: Aldrin Piri Assignee: Aldrin Piri >From the 1.11 release vote [~kdoran] reported an issue with the Docker build >working via Maven. >(https://lists.apache.org/thread.html/r6d7c3298249511d60e386f7aa3107cdf225d48a70ead1251780f0cb1%40%3Cdev.nifi.apache.org%3E). This is the result of our zip source which does not preserve permissions and makes it such that the associated script files are not executable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Deleted] (MINIFICPP-1130) Install of minifi as a service via minfi.sh does not complete successfully
[
https://issues.apache.org/jira/browse/MINIFICPP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri deleted MINIFICPP-1130:
---
> Install of minifi as a service via minfi.sh does not complete successfully
> --
>
> Key: MINIFICPP-1130
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1130
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
>Reporter: Aldrin Piri
>Priority: Major
>
> On RHEL/CentOS 7 trying to install leads to the following error:
> {quote}[root@4d66d22dfec0 nifi-minifi-cpp-0.7.0]# ./bin/minifi.sh install
> minifi
> ./bin/minifi.sh: line 120: % 5: syntax error: operand expected (error token
> is "% 5")
> Could not create service file /etc/init.d/minifi
> {quote}
> This can be recreated with the following, brute force, Docker-based one liner:
> {code:java}
> docker run -it centos:7 /bin/bash -c "yum install -y wget; cd; mkdir minifi:
> cd minifi; wget
> http://mirror.olnevhost.net/pub/apache/nifi/nifi-minifi-cpp/0.7.0/nifi-minifi-cpp-centos-0.7.0-bin.tar.gz;
> tar xf nifi-minifi-cpp-centos-0.7.0-bin.tar.gz; cd nifi-minifi-cpp-0.7.0/;
> ./bin/minifi.sh install minifi"{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MINIFICPP-1131) MiNiFi cpp-0.7.0 installation on rhel7 failing
[
https://issues.apache.org/jira/browse/MINIFICPP-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025113#comment-17025113
]
Aldrin Piri commented on MINIFICPP-1131:
This can be recreated with the following, brute force, Docker-based one liner:
{code:java}
docker run -it centos:7 /bin/bash -c "yum install -y wget; cd; mkdir minifi: cd
minifi; wget
http://mirror.olnevhost.net/pub/apache/nifi/nifi-minifi-cpp/0.7.0/nifi-minifi-cpp-centos-0.7.0-bin.tar.gz;
tar xf nifi-minifi-cpp-centos-0.7.0-bin.tar.gz; cd nifi-minifi-cpp-0.7.0/;
./bin/minifi.sh install minifi"{code}
> MiNiFi cpp-0.7.0 installation on rhel7 failing
> ---
>
> Key: MINIFICPP-1131
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1131
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
>Affects Versions: 0.7.0
> Environment: MiNiFi++ cpp-0.7.0
> RHEL/CentOS 7
>Reporter: CHANDAN KUMAR
>Priority: Major
>
> # ./minifi.sh install dataflow
> ./minifi.sh: line 120: % 5: syntax error: operand expected (error token is "%
> 5")
> Could not create service file /etc/init.d/dataflow
>
> I see few more lines of code added in minifi.sh script in cpp-0.7.0 as
> compare to cpp-0.6.0 (Commenting out lines 169 to 279 seems to solve the
> problem)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Moved] (MINIFICPP-1131) MiNiFi cpp-0.7.0 installation on rhel7 failing
[ https://issues.apache.org/jira/browse/MINIFICPP-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri moved NIFI-7071 to MINIFICPP-1131: -- Component/s: (was: Configuration) Key: MINIFICPP-1131 (was: NIFI-7071) Affects Version/s: (was: 0.7.0) 0.7.0 Project: Apache NiFi MiNiFi C++ (was: Apache NiFi) > MiNiFi cpp-0.7.0 installation on rhel7 failing > --- > > Key: MINIFICPP-1131 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1131 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Affects Versions: 0.7.0 > Environment: MiNiFi++ cpp-0.7.0 > RHEL/CentOS 7 >Reporter: CHANDAN KUMAR >Priority: Major > Labels: triage > > # ./minifi.sh install dataflow > ./minifi.sh: line 120: % 5: syntax error: operand expected (error token is "% > 5") > Could not create service file /etc/init.d/dataflow > > I see few more lines of code added in minifi.sh script in cpp-0.7.0 as > compare to cpp-0.6.0 (Commenting out lines 169 to 279 seems to solve the > problem) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1131) MiNiFi cpp-0.7.0 installation on rhel7 failing
[ https://issues.apache.org/jira/browse/MINIFICPP-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1131: --- Labels: (was: triage) > MiNiFi cpp-0.7.0 installation on rhel7 failing > --- > > Key: MINIFICPP-1131 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1131 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Affects Versions: 0.7.0 > Environment: MiNiFi++ cpp-0.7.0 > RHEL/CentOS 7 >Reporter: CHANDAN KUMAR >Priority: Major > > # ./minifi.sh install dataflow > ./minifi.sh: line 120: % 5: syntax error: operand expected (error token is "% > 5") > Could not create service file /etc/init.d/dataflow > > I see few more lines of code added in minifi.sh script in cpp-0.7.0 as > compare to cpp-0.6.0 (Commenting out lines 169 to 279 seems to solve the > problem) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1130) Install of minifi as a service via minfi.sh does not complete successfully
Aldrin Piri created MINIFICPP-1130:
--
Summary: Install of minifi as a service via minfi.sh does not
complete successfully
Key: MINIFICPP-1130
URL: https://issues.apache.org/jira/browse/MINIFICPP-1130
Project: Apache NiFi MiNiFi C++
Issue Type: Improvement
Affects Versions: 0.7.0
Reporter: Aldrin Piri
On RHEL/CentOS 7 trying to install leads to the following error:
{quote}[root@4d66d22dfec0 nifi-minifi-cpp-0.7.0]# ./bin/minifi.sh install minifi
./bin/minifi.sh: line 120: % 5: syntax error: operand expected (error token is
"% 5")
Could not create service file /etc/init.d/minifi
{quote}
This can be recreated with the following, brute force, Docker-based one liner:
{code:java}
docker run -it centos:7 /bin/bash -c "yum install -y wget; cd; mkdir minifi: cd
minifi; wget
http://mirror.olnevhost.net/pub/apache/nifi/nifi-minifi-cpp/0.7.0/nifi-minifi-cpp-centos-0.7.0-bin.tar.gz;
tar xf nifi-minifi-cpp-centos-0.7.0-bin.tar.gz; cd nifi-minifi-cpp-0.7.0/;
./bin/minifi.sh install minifi"{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MINIFICPP-1091) Update README.md, PROCESSORS.md, Windows.md, *.md, LICENSE, NOTICE for 0.7.0 release
[ https://issues.apache.org/jira/browse/MINIFICPP-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFICPP-1091: -- Assignee: Dániel Bakai > Update README.md, PROCESSORS.md, Windows.md, *.md, LICENSE, NOTICE for 0.7.0 > release > > > Key: MINIFICPP-1091 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1091 > Project: Apache NiFi MiNiFi C++ > Issue Type: Documentation >Reporter: Dániel Bakai >Assignee: Dániel Bakai >Priority: Blocker > Fix For: 0.7.0 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Ensure that all changes since 0.6.0 are reflected in these documents. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1091) Update README.md, PROCESSORS.md, Windows.md, *.md, LICENSE, NOTICE for 0.7.0 release
[ https://issues.apache.org/jira/browse/MINIFICPP-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-1091. Resolution: Fixed > Update README.md, PROCESSORS.md, Windows.md, *.md, LICENSE, NOTICE for 0.7.0 > release > > > Key: MINIFICPP-1091 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1091 > Project: Apache NiFi MiNiFi C++ > Issue Type: Documentation >Reporter: Dániel Bakai >Priority: Blocker > Fix For: 0.7.0 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Ensure that all changes since 0.6.0 are reflected in these documents. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1108) Automate the generation of processors.md
[ https://issues.apache.org/jira/browse/MINIFICPP-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-1108. Fix Version/s: 0.7.0 Resolution: Fixed > Automate the generation of processors.md > > > Key: MINIFICPP-1108 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1108 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Arpad Boda >Assignee: Arpad Boda >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Add a code and command line arg to MiNiFi to be able to generate processor > documentation automatically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1109) Update PROCESSORS.md to be alligned with latest changes
[ https://issues.apache.org/jira/browse/MINIFICPP-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1109: --- Fix Version/s: 0.7.0 > Update PROCESSORS.md to be alligned with latest changes > --- > > Key: MINIFICPP-1109 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1109 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Arpad Boda >Assignee: Arpad Boda >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > PROCESSORS.md is outdated and missing some processors, should be updated to > be aligned with the current source code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1109) Update PROCESSORS.md to be alligned with latest changes
[ https://issues.apache.org/jira/browse/MINIFICPP-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-1109. Resolution: Fixed > Update PROCESSORS.md to be alligned with latest changes > --- > > Key: MINIFICPP-1109 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1109 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Arpad Boda >Assignee: Arpad Boda >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > PROCESSORS.md is outdated and missing some processors, should be updated to > be aligned with the current source code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1079) Provide a listing of extensions/components on startup
Aldrin Piri created MINIFICPP-1079: -- Summary: Provide a listing of extensions/components on startup Key: MINIFICPP-1079 URL: https://issues.apache.org/jira/browse/MINIFICPP-1079 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri It would be helpful to provide a listing of components such that we can better identify config/build issues for users when they are running minifi. This would mimic the functionality we have in NiFi/MiNiFi Java. This should also include extended components such as those provided via JNI or based in python. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6848) Migrate NiFi Site to ASF git build/deploy
Aldrin Piri created NIFI-6848: - Summary: Migrate NiFi Site to ASF git build/deploy Key: NIFI-6848 URL: https://issues.apache.org/jira/browse/NIFI-6848 Project: Apache NiFi Issue Type: Task Components: Documentation Website Reporter: Aldrin Piri Currently, NiFi's site is versioned in https://gitbox.apache.org/repos/asf?p=nifi-site.git but a scripted process via grunt, manually executed, is used to publish this site to the legacy CMS (svn) system. The CMS system is largely deprecated and targeted for EOL in the upcoming months. We should look to transition our repository/site over to the new approach outlined at https://s.apache.org/asfyaml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1075) Heartbeats over CoAP are incomplete when running with empty flow
Aldrin Piri created MINIFICPP-1075: -- Summary: Heartbeats over CoAP are incomplete when running with empty flow Key: MINIFICPP-1075 URL: https://issues.apache.org/jira/browse/MINIFICPP-1075 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Affects Versions: 0.6.0 Reporter: Aldrin Piri Fix For: 0.7.0 In the event that the CoAP protocol is used but the instance has an empty config.yml there will be an ignorable PayloadParseException about queues not being available but this precludes the rest of the hearbeat from being formed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-1377) Upgrade to JsonPath 2.2.0
[ https://issues.apache.org/jira/browse/NIFI-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-1377. --- Resolution: Won't Fix > Upgrade to JsonPath 2.2.0 > - > > Key: NIFI-1377 > URL: https://issues.apache.org/jira/browse/NIFI-1377 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Aldrin Piri >Priority: Minor > > JsonPath (https://github.com/jayway/JsonPath) has a new release. > Given some of the optimizations that were made for the processors to provide > caching of and validation without exceptions of expressions, it is not a > clean upgrade due to those library internals being removed and/or changed. > Additionally, a new caching mechanism for expressions was also provided that > may be beneficial to make use of. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-1377) Upgrade to JsonPath 2.2.0
[ https://issues.apache.org/jira/browse/NIFI-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960697#comment-16960697 ] Aldrin Piri commented on NIFI-1377: --- [~janh] certainly can and good find > Upgrade to JsonPath 2.2.0 > - > > Key: NIFI-1377 > URL: https://issues.apache.org/jira/browse/NIFI-1377 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Aldrin Piri >Priority: Minor > > JsonPath (https://github.com/jayway/JsonPath) has a new release. > Given some of the optimizations that were made for the processors to provide > caching of and validation without exceptions of expressions, it is not a > clean upgrade due to those library internals being removed and/or changed. > Additionally, a new caching mechanism for expressions was also provided that > may be beneficial to make use of. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Moved] (NIFIREG-341) Update README to make use of ASF url for community slack channel
[ https://issues.apache.org/jira/browse/NIFIREG-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri moved NIFI-6810 to NIFIREG-341: --- Key: NIFIREG-341 (was: NIFI-6810) Workflow: jira (was: patch-available, re-open possible) Project: NiFi Registry (was: Apache NiFi) > Update README to make use of ASF url for community slack channel > > > Key: NIFIREG-341 > URL: https://issues.apache.org/jira/browse/NIFIREG-341 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Trivial > > We can use the shortened URL https://s.apache.org/nifi-community-slack to > point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6810) Update README to make use of ASF url for community slack channel
Aldrin Piri created NIFI-6810: - Summary: Update README to make use of ASF url for community slack channel Key: NIFI-6810 URL: https://issues.apache.org/jira/browse/NIFI-6810 Project: Apache NiFi Issue Type: Improvement Reporter: Aldrin Piri Assignee: Aldrin Piri We can use the shortened URL https://s.apache.org/nifi-community-slack to point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6809) Update README to make use of ASF url for community slack channel
[ https://issues.apache.org/jira/browse/NIFI-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-6809: -- Priority: Trivial (was: Major) > Update README to make use of ASF url for community slack channel > > > Key: NIFI-6809 > URL: https://issues.apache.org/jira/browse/NIFI-6809 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Trivial > Time Spent: 10m > Remaining Estimate: 0h > > We can use the shortened URL https://s.apache.org/nifi-community-slack to > point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6809) Update README to make use of ASF url for community slack channel
[ https://issues.apache.org/jira/browse/NIFI-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-6809: -- Status: Patch Available (was: Open) > Update README to make use of ASF url for community slack channel > > > Key: NIFI-6809 > URL: https://issues.apache.org/jira/browse/NIFI-6809 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We can use the shortened URL https://s.apache.org/nifi-community-slack to > point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6809) Update README to make use of ASF url for community slack channel
Aldrin Piri created NIFI-6809: - Summary: Update README to make use of ASF url for community slack channel Key: NIFI-6809 URL: https://issues.apache.org/jira/browse/NIFI-6809 Project: Apache NiFi Issue Type: Improvement Reporter: Aldrin Piri Assignee: Aldrin Piri We can use the shortened URL https://s.apache.org/nifi-community-slack to point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1025) CWEL should output event messages
[ https://issues.apache.org/jira/browse/MINIFICPP-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-1025. Fix Version/s: 0.7.0 Resolution: Fixed > CWEL should output event messages > - > > Key: MINIFICPP-1025 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1025 > Project: Apache NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Marc Parisi >Assignee: Marc Parisi >Priority: Major > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > CWEL should output event messages -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1064) Provide a bored yield duration for timer driven scheduling
[ https://issues.apache.org/jira/browse/MINIFICPP-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-1064. Resolution: Invalid > Provide a bored yield duration for timer driven scheduling > -- > > Key: MINIFICPP-1064 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1064 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Aldrin Piri >Priority: Major > > Currently when a processor is scheduled with a zero scheduling period it will > be scheduled repeatedly. While this is literally what is requested, it can > be problematic when there is no work to be done. NiFi remedies this by > incorporating a bored yield period (defaulting to 10ms) which helps to dampen > the effects of a processor with no work to do. See > https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/TimerDrivenSchedulingAgent.java#L56 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1064) Provide a bored yield duration for timer driven scheduling
Aldrin Piri created MINIFICPP-1064: -- Summary: Provide a bored yield duration for timer driven scheduling Key: MINIFICPP-1064 URL: https://issues.apache.org/jira/browse/MINIFICPP-1064 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri Currently when a processor is scheduled with a zero scheduling period it will be scheduled repeatedly. While this is literally what is requested, it can be problematic when there is no work to be done. NiFi remedies this by incorporating a bored yield period (defaulting to 10ms) which helps to dampen the effects of a processor with no work to do. See https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/TimerDrivenSchedulingAgent.java#L56 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1063) Log directory location should be configurable
Aldrin Piri created MINIFICPP-1063: -- Summary: Log directory location should be configurable Key: MINIFICPP-1063 URL: https://issues.apache.org/jira/browse/MINIFICPP-1063 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri minifi-log.properties allows specification of log name via appender.rolling.file_name but location is hardcoded to be in $MINIFI_HOME/logs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-6733) Create Apache NiFi 1.10.0 Release
[ https://issues.apache.org/jira/browse/NIFI-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-6733. --- Resolution: Fixed > Create Apache NiFi 1.10.0 Release > - > > Key: NIFI-6733 > URL: https://issues.apache.org/jira/browse/NIFI-6733 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Affects Versions: 1.10.0 >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6747) Swagger REST API uses old logo
Aldrin Piri created NIFI-6747: - Summary: Swagger REST API uses old logo Key: NIFI-6747 URL: https://issues.apache.org/jira/browse/NIFI-6747 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Reporter: Aldrin Piri The Swagger REST API (/nifi-docs/rest-api/index.html) makes use of the old, 0.x logo and not that of the 1.x line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1052) Remove extraneous files from thirdparty dependencies
[ https://issues.apache.org/jira/browse/MINIFICPP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1052: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove extraneous files from thirdparty dependencies > > > Key: MINIFICPP-1052 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1052 > Project: Apache NiFi MiNiFi C++ > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Should prefer to remove third party examples/docs and the like that may have > hard traceability to their origins to ensure accuracy of our L -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1052) Remove extraneous files from thirdparty dependencies
[ https://issues.apache.org/jira/browse/MINIFICPP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1052: --- Status: Patch Available (was: Open) > Remove extraneous files from thirdparty dependencies > > > Key: MINIFICPP-1052 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1052 > Project: Apache NiFi MiNiFi C++ > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 0.7.0 > > > Should prefer to remove third party examples/docs and the like that may have > hard traceability to their origins to ensure accuracy of our L -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-530) Cleanup unnecessary resources in thirdparty libraries
[ https://issues.apache.org/jira/browse/MINIFICPP-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-530. --- Resolution: Duplicate > Cleanup unnecessary resources in thirdparty libraries > - > > Key: MINIFICPP-530 > URL: https://issues.apache.org/jira/browse/MINIFICPP-530 > Project: Apache NiFi MiNiFi C++ > Issue Type: Task >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > > Some libraries included in thirdparty have example files and resources that > are not pertinent to our project and expand the footprint of our L > concerns. Cleaning these up would limit our exposure to files whose lineage > may be uncertain. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1011) Docker build is broken
[ https://issues.apache.org/jira/browse/MINIFICPP-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1011: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Docker build is broken > -- > > Key: MINIFICPP-1011 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1011 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > With the changes to support packaging of MSI name changes are affecting the > `docker` target of our build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFICPP-1012) Provide a latest/current symlink for Docker image to reach MINIFI_HOME
[ https://issues.apache.org/jira/browse/MINIFICPP-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1012: --- Fix Version/s: 0.7.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Provide a latest/current symlink for Docker image to reach MINIFI_HOME > -- > > Key: MINIFICPP-1012 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1012 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.6.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > We should add a symlink of latest/current to the MINIFI_HOME that serves as a > static way to access the working directory. We have done this elsewhere in > Docker images in the nifi community and it would allow a more seamless > transition between versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1052) Remove extraneous files from thirdparty dependencies
Aldrin Piri created MINIFICPP-1052: -- Summary: Remove extraneous files from thirdparty dependencies Key: MINIFICPP-1052 URL: https://issues.apache.org/jira/browse/MINIFICPP-1052 Project: Apache NiFi MiNiFi C++ Issue Type: Task Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.7.0 Should prefer to remove third party examples/docs and the like that may have hard traceability to their origins to ensure accuracy of our L -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFICPP-1041) Re-order connection queues in RESTFuil c2 response
[ https://issues.apache.org/jira/browse/MINIFICPP-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-1041. Resolution: Fixed > Re-order connection queues in RESTFuil c2 response > --- > > Key: MINIFICPP-1041 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1041 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Marc Parisi >Assignee: Marc Parisi >Priority: Major > Fix For: 0.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Currently the JSON response has the queue name as the top level node ( in > jSON this is the object key ). We don't want to change the AST and impact > upstream changes. Therefore we will simply change the JSON response in line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFICPP-1049) Docker target currently broken
Aldrin Piri created MINIFICPP-1049:
--
Summary: Docker target currently broken
Key: MINIFICPP-1049
URL: https://issues.apache.org/jira/browse/MINIFICPP-1049
Project: Apache NiFi MiNiFi C++
Issue Type: Bug
Reporter: Aldrin Piri
The docker target is currently broken on master.
Running `make docker` provides:
{quote}CMake Error at CMakeLists.txt:196 (include):
include could not find load file:
LibreSSL
CMake Error at CMakeLists.txt:197 (use_libre_ssl):
Unknown CMake command "use_libre_ssl".
-- Configuring incomplete, errors occurred!
See also "/opt/minifi/build/CMakeFiles/CMakeOutput.log".
See also "/opt/minifi/build/CMakeFiles/CMakeError.log".{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (NIFI-6713) CLONE - Updated bootstrap port handling causes restarts to fail
Aldrin Piri created NIFI-6713:
-
Summary: CLONE - Updated bootstrap port handling causes restarts
to fail
Key: NIFI-6713
URL: https://issues.apache.org/jira/browse/NIFI-6713
Project: Apache NiFi
Issue Type: Bug
Reporter: Aldrin Piri
Assignee: Aldrin Piri
Fix For: 1.10.0
NIFI-6653 introduced a way to avoid the port being changed to prevent a
possible hijacking of that port to provide other commands than those explicitly
between bootstrap and the nifi process. This causes issues when the NiFi
process dies and precludes restart (the default functionality enabled out of
the box).
To recreate, build/run NiFi off of current master and kill the NiFi process.
This will result in the following (when an additional nifi.sh status is carried
out).
{quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
Apache NiFi appears to have died. Restarting...
2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command Launched
Apache NiFi with Process ID 2088
2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Successfully started Apache NiFi with PID 2088
2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command port
and secret after they have already been initialized. requestedPort=37871
2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
Successfully loaded the following 0 services: []
2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STARTED
2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STOPPED
2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_DIED
2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (NIFIREG-323) CLONE - Updated bootstrap port handling causes restarts to fail
[
https://issues.apache.org/jira/browse/NIFIREG-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938082#comment-16938082
]
Aldrin Piri commented on NIFIREG-323:
-
This was done against NIFIREG-318 for registry.
> CLONE - Updated bootstrap port handling causes restarts to fail
> ---
>
> Key: NIFIREG-323
> URL: https://issues.apache.org/jira/browse/NIFIREG-323
> Project: NiFi Registry
> Issue Type: Bug
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Blocker
>
> NIFI-6653 introduced a way to avoid the port being changed to prevent a
> possible hijacking of that port to provide other commands than those
> explicitly between bootstrap and the nifi process. This causes issues when
> the NiFi process dies and precludes restart (the default functionality
> enabled out of the box).
> To recreate, build/run NiFi off of current master and kill the NiFi process.
> This will result in the following (when an additional nifi.sh status is
> carried out).
> {quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
> Apache NiFi appears to have died. Restarting...
> 2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 2088
> 2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Successfully started Apache NiFi with PID 2088
> 2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command
> port and secret after they have already been initialized. requestedPort=37871
> 2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
> NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Moved] (NIFIREG-323) CLONE - Updated bootstrap port handling causes restarts to fail
[
https://issues.apache.org/jira/browse/NIFIREG-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri moved NIFI-6712 to NIFIREG-323:
---
Fix Version/s: (was: 1.10.0)
Key: NIFIREG-323 (was: NIFI-6712)
Workflow: jira (was: patch-available, re-open possible)
Project: NiFi Registry (was: Apache NiFi)
> CLONE - Updated bootstrap port handling causes restarts to fail
> ---
>
> Key: NIFIREG-323
> URL: https://issues.apache.org/jira/browse/NIFIREG-323
> Project: NiFi Registry
> Issue Type: Bug
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Blocker
>
> NIFI-6653 introduced a way to avoid the port being changed to prevent a
> possible hijacking of that port to provide other commands than those
> explicitly between bootstrap and the nifi process. This causes issues when
> the NiFi process dies and precludes restart (the default functionality
> enabled out of the box).
> To recreate, build/run NiFi off of current master and kill the NiFi process.
> This will result in the following (when an additional nifi.sh status is
> carried out).
> {quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
> Apache NiFi appears to have died. Restarting...
> 2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 2088
> 2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Successfully started Apache NiFi with PID 2088
> 2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command
> port and secret after they have already been initialized. requestedPort=37871
> 2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
> NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (NIFI-6712) CLONE - Updated bootstrap port handling causes restarts to fail
Aldrin Piri created NIFI-6712:
-
Summary: CLONE - Updated bootstrap port handling causes restarts
to fail
Key: NIFI-6712
URL: https://issues.apache.org/jira/browse/NIFI-6712
Project: Apache NiFi
Issue Type: Bug
Reporter: Aldrin Piri
Assignee: Aldrin Piri
Fix For: 1.10.0
NIFI-6653 introduced a way to avoid the port being changed to prevent a
possible hijacking of that port to provide other commands than those explicitly
between bootstrap and the nifi process. This causes issues when the NiFi
process dies and precludes restart (the default functionality enabled out of
the box).
To recreate, build/run NiFi off of current master and kill the NiFi process.
This will result in the following (when an additional nifi.sh status is carried
out).
{quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
Apache NiFi appears to have died. Restarting...
2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command Launched
Apache NiFi with Process ID 2088
2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Successfully started Apache NiFi with PID 2088
2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command port
and secret after they have already been initialized. requestedPort=37871
2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
Successfully loaded the following 0 services: []
2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STARTED
2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STOPPED
2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_DIED
2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (NIFI-6711) Updated bootstrap port handling causes restarts to fail
Aldrin Piri created NIFI-6711:
-
Summary: Updated bootstrap port handling causes restarts to fail
Key: NIFI-6711
URL: https://issues.apache.org/jira/browse/NIFI-6711
Project: Apache NiFi
Issue Type: Bug
Reporter: Aldrin Piri
Assignee: Aldrin Piri
Fix For: 1.10.0
NIFI-6653 introduced a way to avoid the port being changed to prevent a
possible hijacking of that port to provide other commands than those explicitly
between bootstrap and the nifi process. This causes issues when the NiFi
process dies and precludes restart (the default functionality enabled out of
the box).
To recreate, build/run NiFi off of current master and kill the NiFi process.
This will result in the following (when an additional nifi.sh status is carried
out).
{quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
Apache NiFi appears to have died. Restarting...
2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command Launched
Apache NiFi with Process ID 2088
2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Successfully started Apache NiFi with PID 2088
2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command port
and secret after they have already been initialized. requestedPort=37871
2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
Successfully loaded the following 0 services: []
2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STARTED
2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STOPPED
2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_DIED
2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-6604) Reduce the size of the generated assemblies
[ https://issues.apache.org/jira/browse/NIFI-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-6604: -- Status: Patch Available (was: Open) > Reduce the size of the generated assemblies > --- > > Key: NIFI-6604 > URL: https://issues.apache.org/jira/browse/NIFI-6604 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 1.10.0 > > Time Spent: 10m > Remaining Estimate: 0h > > As per the discussion on > https://lists.apache.org/thread.html/d45f33805dcb8096914a06853bc3b8eca1acf50c2ae7b68e75eabfe8@ > we must reduce the assembly size such that we can publish the convenience > binaries as part of the release. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6604) Reduce the size of the generated assemblies
Aldrin Piri created NIFI-6604: - Summary: Reduce the size of the generated assemblies Key: NIFI-6604 URL: https://issues.apache.org/jira/browse/NIFI-6604 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 1.10.0 As per the discussion on https://lists.apache.org/thread.html/d45f33805dcb8096914a06853bc3b8eca1acf50c2ae7b68e75eabfe8@ we must reduce the assembly size such that we can publish the convenience binaries as part of the release. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (NIFI-6584) Recognize $JAVA_HOME changes via the Terminal
[
https://issues.apache.org/jira/browse/NIFI-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri resolved NIFI-6584.
---
Resolution: Not A Problem
> Recognize $JAVA_HOME changes via the Terminal
> -
>
> Key: NIFI-6584
> URL: https://issues.apache.org/jira/browse/NIFI-6584
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: Distributor ID: Ubuntu
> Description: Ubuntu 18.04.3 LTS
> Release: 18.04
> Codename: bionic
> https://github.com/jenv/jenv
>Reporter: Ben Stuart
>Priority: Major
>
> I've been notified NiFi dosen't support java11 yet and suspect that is the
> reason Nifi won't lunch.
> I am trying to get around this by using jenv.
> Having a look at the screenshot below you can see when I launch NiFi it
> believes the java home is still set to Java11.
> I suspected it's realted to this: [https://github.com/jenv/jenv/issues/224]
> in summary, I suspect NiFi is pointing to a full static path to the java file
> opposed to referencing $JAVA_HOME
> I'm hoping if this is the case, it can be improved to recognize the change
> better.
> {code:java}
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ jenv versions
> system
> 11.0
> 11.0.4
> * 1.8 (set by JENV_VERSION environment variable)
> 1.8.0.202
> openjdk64-11.0.4
> oracle64-1.8.0.202
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ java -version
> java version "1.8.0_202"
> Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$ sudo ./nifi.sh run
> Java home: /usr/lib/jvm/java-11-openjdk-amd64
> NiFi home: /home/ben/Downloads/nifi-1.9.2
> Bootstrap Config File: /home/ben
> /Downloads/nifi-1.9.2/conf/bootstrap.conf2019-08-23 10:36:59,977 INFO [main]
> org.apache.nifi.bootstrap.Command Starting Apache NiFi...
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command Working
> Directory: /home/ben/Downloads/nifi-1.9.2
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command
> Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -classpath
> /home/ben/Downloads/nifi-1.9.2/./conf:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-runtime-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-framework-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jcl-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/slf4j-api-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-properties-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/log4j-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-core-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/javax.servlet-api-3.1.0.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jetty-schemas-3.1.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-classic-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jul-to-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-nar-utils-1.9.2.jar
> -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m
> -Djavax.security.auth.useSubjectCredsOnly=true
> -Djava.security.egd=file:/dev/urandom
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol
> -XX:+UseG1GC
> -Dnifi.properties.file.path=/home/ben/Downloads/nifi-1.9.2/./conf/nifi.properties
> -Dnifi.bootstrap.listen.port=35343 -Dapp=NiFi
> -Dorg.apache.nifi.bootstrap.config.log.dir=/home/ben/Downloads/nifi-1.9.2/logs
> --add-modules=java.xml.bind org.apache.nifi.NiFi
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.apache.nifi.bootstrap.util.OSUtils
> (file:/home/ben/Downloads/nifi-1.9.2/lib/bootstrap/nifi-bootstrap-1.9.2.jar)
> to method java.lang.ProcessImpl.pid()
> WARNING: Please consider reporting this to the maintainers of
> org.apache.nifi.bootstrap.util.OSUtils
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 2019-08-23 10:36:59,992 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 22931
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (NIFI-6584) Recognize $JAVA_HOME changes via the Terminal
[
https://issues.apache.org/jira/browse/NIFI-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914363#comment-16914363
]
Aldrin Piri commented on NIFI-6584:
---
Glad to hear you got it working with the desired Java version. I'm going to
resolve this ticket as a result of the issue being tied to issues with
environment.
Not sure why those file access issues arose but should not be a problem with
our assembly as supplied. Is it possible that file was owned by another user?
Can you provide steps to reproduce the error? If so, would you mind opening
another ticket such that we can try to track down that bug.
> Recognize $JAVA_HOME changes via the Terminal
> -
>
> Key: NIFI-6584
> URL: https://issues.apache.org/jira/browse/NIFI-6584
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: Distributor ID: Ubuntu
> Description: Ubuntu 18.04.3 LTS
> Release: 18.04
> Codename: bionic
> https://github.com/jenv/jenv
>Reporter: Ben Stuart
>Priority: Major
>
> I've been notified NiFi dosen't support java11 yet and suspect that is the
> reason Nifi won't lunch.
> I am trying to get around this by using jenv.
> Having a look at the screenshot below you can see when I launch NiFi it
> believes the java home is still set to Java11.
> I suspected it's realted to this: [https://github.com/jenv/jenv/issues/224]
> in summary, I suspect NiFi is pointing to a full static path to the java file
> opposed to referencing $JAVA_HOME
> I'm hoping if this is the case, it can be improved to recognize the change
> better.
> {code:java}
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ jenv versions
> system
> 11.0
> 11.0.4
> * 1.8 (set by JENV_VERSION environment variable)
> 1.8.0.202
> openjdk64-11.0.4
> oracle64-1.8.0.202
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ java -version
> java version "1.8.0_202"
> Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$ sudo ./nifi.sh run
> Java home: /usr/lib/jvm/java-11-openjdk-amd64
> NiFi home: /home/ben/Downloads/nifi-1.9.2
> Bootstrap Config File: /home/ben
> /Downloads/nifi-1.9.2/conf/bootstrap.conf2019-08-23 10:36:59,977 INFO [main]
> org.apache.nifi.bootstrap.Command Starting Apache NiFi...
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command Working
> Directory: /home/ben/Downloads/nifi-1.9.2
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command
> Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -classpath
> /home/ben/Downloads/nifi-1.9.2/./conf:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-runtime-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-framework-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jcl-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/slf4j-api-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-properties-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/log4j-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-core-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/javax.servlet-api-3.1.0.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jetty-schemas-3.1.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-classic-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jul-to-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-nar-utils-1.9.2.jar
> -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m
> -Djavax.security.auth.useSubjectCredsOnly=true
> -Djava.security.egd=file:/dev/urandom
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol
> -XX:+UseG1GC
> -Dnifi.properties.file.path=/home/ben/Downloads/nifi-1.9.2/./conf/nifi.properties
> -Dnifi.bootstrap.listen.port=35343 -Dapp=NiFi
> -Dorg.apache.nifi.bootstrap.config.log.dir=/home/ben/Downloads/nifi-1.9.2/logs
> --add-modules=java.xml.bind org.apache.nifi.NiFi
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.apache.nifi.bootstrap.util.OSUtils
> (file:/home/ben/Downloads/nifi-1.9.2/lib/bootstrap/nifi-bootstrap-1.9.2.jar)
> to method java.lang.ProcessImpl.pid()
> WARNING: Please consider reporting this to the maintainers of
> org.apache.nifi.bootstrap.util.OSUtils
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 2019-08-23 10:36:59,992 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 22931
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$
> {code}
>
--
This message was sent by Atlassian Jira
[jira] [Updated] (NIFI-6584) Recognize $JAVA_HOME changes via the Terminal
[
https://issues.apache.org/jira/browse/NIFI-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated NIFI-6584:
--
Fix Version/s: (was: 1.9.1)
> Recognize $JAVA_HOME changes via the Terminal
> -
>
> Key: NIFI-6584
> URL: https://issues.apache.org/jira/browse/NIFI-6584
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: Distributor ID: Ubuntu
> Description: Ubuntu 18.04.3 LTS
> Release: 18.04
> Codename: bionic
> https://github.com/jenv/jenv
>Reporter: Ben Stuart
>Priority: Major
>
> I've been notified NiFi dosen't support java11 yet and suspect that is the
> reason Nifi won't lunch.
> I am trying to get around this by using jenv.
> Having a look at the screenshot below you can see when I launch NiFi it
> believes the java home is still set to Java11.
> I suspected it's realted to this: [https://github.com/jenv/jenv/issues/224]
> in summary, I suspect NiFi is pointing to a full static path to the java file
> opposed to referencing $JAVA_HOME
> I'm hoping if this is the case, it can be improved to recognize the change
> better.
> {code:java}
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ jenv versions
> system
> 11.0
> 11.0.4
> * 1.8 (set by JENV_VERSION environment variable)
> 1.8.0.202
> openjdk64-11.0.4
> oracle64-1.8.0.202
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ java -version
> java version "1.8.0_202"
> Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$ sudo ./nifi.sh run
> Java home: /usr/lib/jvm/java-11-openjdk-amd64
> NiFi home: /home/ben/Downloads/nifi-1.9.2
> Bootstrap Config File: /home/ben
> /Downloads/nifi-1.9.2/conf/bootstrap.conf2019-08-23 10:36:59,977 INFO [main]
> org.apache.nifi.bootstrap.Command Starting Apache NiFi...
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command Working
> Directory: /home/ben/Downloads/nifi-1.9.2
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command
> Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -classpath
> /home/ben/Downloads/nifi-1.9.2/./conf:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-runtime-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-framework-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jcl-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/slf4j-api-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-properties-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/log4j-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-core-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/javax.servlet-api-3.1.0.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jetty-schemas-3.1.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-classic-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jul-to-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-nar-utils-1.9.2.jar
> -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m
> -Djavax.security.auth.useSubjectCredsOnly=true
> -Djava.security.egd=file:/dev/urandom
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol
> -XX:+UseG1GC
> -Dnifi.properties.file.path=/home/ben/Downloads/nifi-1.9.2/./conf/nifi.properties
> -Dnifi.bootstrap.listen.port=35343 -Dapp=NiFi
> -Dorg.apache.nifi.bootstrap.config.log.dir=/home/ben/Downloads/nifi-1.9.2/logs
> --add-modules=java.xml.bind org.apache.nifi.NiFi
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.apache.nifi.bootstrap.util.OSUtils
> (file:/home/ben/Downloads/nifi-1.9.2/lib/bootstrap/nifi-bootstrap-1.9.2.jar)
> to method java.lang.ProcessImpl.pid()
> WARNING: Please consider reporting this to the maintainers of
> org.apache.nifi.bootstrap.util.OSUtils
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 2019-08-23 10:36:59,992 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 22931
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (NIFI-6584) Recognize $JAVA_HOME changes via the Terminal
[
https://issues.apache.org/jira/browse/NIFI-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913842#comment-16913842
]
Aldrin Piri commented on NIFI-6584:
---
Hi [~bennyboi],
I do believe we make use of JAVA_HOME. The relevant section is here:
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/bin/nifi.sh#L121-L155.
We have no static references to any files in that script. We do make a best
effort if all the normal avenues fail, but that outputs "JAVA_HOME not set;
results may vary" as shown at
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/bin/nifi.sh#L138.
This does not seem to be evident in the log you shared with us. I do see you
are running nifi with sudo. Does `sudo jenv versions` also provide the
selected 1.8 version?
Anything in the shared section look amiss to you that we may be overlooking? I
know several folks in the community use jenv on a regular basis (inclusive of
myself) especially as we worked to provide support for building/running on Java
11.
> Recognize $JAVA_HOME changes via the Terminal
> -
>
> Key: NIFI-6584
> URL: https://issues.apache.org/jira/browse/NIFI-6584
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: Distributor ID: Ubuntu
> Description: Ubuntu 18.04.3 LTS
> Release: 18.04
> Codename: bionic
> https://github.com/jenv/jenv
>Reporter: Ben Stuart
>Priority: Major
> Fix For: 1.9.1
>
>
> I've been notified NiFi dosen't support java11 yet and suspect that is the
> reason Nifi won't lunch.
> I am trying to get around this by using jenv.
> Having a look at the screenshot below you can see when I launch NiFi it
> believes the java home is still set to Java11.
> I suspected it's realted to this: [https://github.com/jenv/jenv/issues/224]
> in summary, I suspect NiFi is pointing to a full static path to the java file
> opposed to referencing $JAVA_HOME
> I'm hoping if this is the case, it can be improved to recognize the change
> better.
> {code:java}
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ jenv versions
> system
> 11.0
> 11.0.4
> * 1.8 (set by JENV_VERSION environment variable)
> 1.8.0.202
> openjdk64-11.0.4
> oracle64-1.8.0.202
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2$ java -version
> java version "1.8.0_202"
> Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
> ben@ben-VirtualBox:~/Downloads/nifi-1.9.2/bin$ sudo ./nifi.sh run
> Java home: /usr/lib/jvm/java-11-openjdk-amd64
> NiFi home: /home/ben/Downloads/nifi-1.9.2
> Bootstrap Config File: /home/ben
> /Downloads/nifi-1.9.2/conf/bootstrap.conf2019-08-23 10:36:59,977 INFO [main]
> org.apache.nifi.bootstrap.Command Starting Apache NiFi...
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command Working
> Directory: /home/ben/Downloads/nifi-1.9.2
> 2019-08-23 10:36:59,977 INFO [main] org.apache.nifi.bootstrap.Command
> Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -classpath
> /home/ben/Downloads/nifi-1.9.2/./conf:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-runtime-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-framework-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jcl-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/slf4j-api-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-properties-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/log4j-over-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-core-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/javax.servlet-api-3.1.0.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-api-1.9.2.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jetty-schemas-3.1.jar:/home/ben/Downloads/nifi-1.9.2/./lib/logback-classic-1.2.3.jar:/home/ben/Downloads/nifi-1.9.2/./lib/jul-to-slf4j-1.7.25.jar:/home/ben/Downloads/nifi-1.9.2/./lib/nifi-nar-utils-1.9.2.jar
> -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m
> -Djavax.security.auth.useSubjectCredsOnly=true
> -Djava.security.egd=file:/dev/urandom
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol
> -XX:+UseG1GC
> -Dnifi.properties.file.path=/home/ben/Downloads/nifi-1.9.2/./conf/nifi.properties
> -Dnifi.bootstrap.listen.port=35343 -Dapp=NiFi
> -Dorg.apache.nifi.bootstrap.config.log.dir=/home/ben/Downloads/nifi-1.9.2/logs
> --add-modules=java.xml.bind org.apache.nifi.NiFi
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.apache.nifi.bootstrap.util.OSUtils
>
[jira] [Updated] (MINIFICPP-1012) Provide a latest/current symlink for Docker image to reach MINIFI_HOME
[ https://issues.apache.org/jira/browse/MINIFICPP-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1012: --- Status: Patch Available (was: Open) > Provide a latest/current symlink for Docker image to reach MINIFI_HOME > -- > > Key: MINIFICPP-1012 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1012 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.6.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We should add a symlink of latest/current to the MINIFI_HOME that serves as a > static way to access the working directory. We have done this elsewhere in > Docker images in the nifi community and it would allow a more seamless > transition between versions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (MINIFICPP-1012) Provide a latest/current symlink for Docker image to reach MINIFI_HOME
Aldrin Piri created MINIFICPP-1012: -- Summary: Provide a latest/current symlink for Docker image to reach MINIFI_HOME Key: MINIFICPP-1012 URL: https://issues.apache.org/jira/browse/MINIFICPP-1012 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Affects Versions: 0.6.0 Reporter: Aldrin Piri Assignee: Aldrin Piri We should add a symlink of latest/current to the MINIFI_HOME that serves as a static way to access the working directory. We have done this elsewhere in Docker images in the nifi community and it would allow a more seamless transition between versions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (MINIFICPP-1011) Docker build is broken
[ https://issues.apache.org/jira/browse/MINIFICPP-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1011: --- Fix Version/s: 0.7.0 > Docker build is broken > -- > > Key: MINIFICPP-1011 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1011 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > With the changes to support packaging of MSI name changes are affecting the > `docker` target of our build. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (MINIFICPP-1011) Docker build is broken
[ https://issues.apache.org/jira/browse/MINIFICPP-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-1011: --- Status: Patch Available (was: In Progress) > Docker build is broken > -- > > Key: MINIFICPP-1011 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1011 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > With the changes to support packaging of MSI name changes are affecting the > `docker` target of our build. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (MINIFICPP-1011) Docker build is broken
Aldrin Piri created MINIFICPP-1011: -- Summary: Docker build is broken Key: MINIFICPP-1011 URL: https://issues.apache.org/jira/browse/MINIFICPP-1011 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Reporter: Aldrin Piri Assignee: Aldrin Piri With the changes to support packaging of MSI name changes are affecting the `docker` target of our build. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (MINIFICPP-34) MINIFI-CPP should run as a Windows service
[ https://issues.apache.org/jira/browse/MINIFICPP-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-34. -- Resolution: Implemented [~cpp] Looks like this was covered by the work in https://github.com/apache/nifi-minifi-cpp/commit/a6876db93676cc43cdfee0b61926b0141c38f91e and the commit that [~phrocker] provided. > MINIFI-CPP should run as a Windows service > -- > > Key: MINIFICPP-34 > URL: https://issues.apache.org/jira/browse/MINIFICPP-34 > Project: Apache NiFi MiNiFi C++ > Issue Type: Sub-task >Reporter: Andre F de Miranda >Assignee: Alex Marmer >Priority: Major > Fix For: 0.7.0 > > > MINIFI-CPP could be a great alternative to tools like nxlog if it was able to: > - Run as a service (MINIFICPP-34) > - Read windows event files (MINIFICPP-32) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (MINIFICPP-34) MINIFI-CPP should run as a Windows service
[ https://issues.apache.org/jira/browse/MINIFICPP-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-34: - Description: MINIFI-CPP could be a great alternative to tools like nxlog if it was able to: - Run as a service (MINIFICPP-34) - Read windows event files (MINIFICPP-32) was: MINIFI-CPP could be a great alternative to tools like nxlog if it was able to: - Run as a service (NIFI-89) - Read windows event files (NIFI-90) > MINIFI-CPP should run as a Windows service > -- > > Key: MINIFICPP-34 > URL: https://issues.apache.org/jira/browse/MINIFICPP-34 > Project: Apache NiFi MiNiFi C++ > Issue Type: Sub-task >Reporter: Andre F de Miranda >Assignee: Alex Marmer >Priority: Major > Fix For: 0.7.0 > > > MINIFI-CPP could be a great alternative to tools like nxlog if it was able to: > - Run as a service (MINIFICPP-34) > - Read windows event files (MINIFICPP-32) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6519) GrokReader does not evaluate EL while validating "Grok Pattern File" property
[ https://issues.apache.org/jira/browse/NIFI-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-6519: -- Fix Version/s: 1.10.0 > GrokReader does not evaluate EL while validating "Grok Pattern File" property > - > > Key: NIFI-6519 > URL: https://issues.apache.org/jira/browse/NIFI-6519 > Project: Apache NiFi > Issue Type: Bug >Reporter: Ferenc Szabo >Assignee: Ferenc Szabo >Priority: Major > Fix For: 1.10.0 > > Time Spent: 10m > Remaining Estimate: 0h > > inside the customValidate method, the PATTERN_FILE property is not evaluated > so users cannot use EL despite the property does support Expression Language -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (NIFI-6519) GrokReader does not evaluate EL while validating "Grok Pattern File" property
[ https://issues.apache.org/jira/browse/NIFI-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-6519. --- Resolution: Fixed > GrokReader does not evaluate EL while validating "Grok Pattern File" property > - > > Key: NIFI-6519 > URL: https://issues.apache.org/jira/browse/NIFI-6519 > Project: Apache NiFi > Issue Type: Bug >Reporter: Ferenc Szabo >Assignee: Ferenc Szabo >Priority: Major > Fix For: 1.10.0 > > Time Spent: 10m > Remaining Estimate: 0h > > inside the customValidate method, the PATTERN_FILE property is not evaluated > so users cannot use EL despite the property does support Expression Language -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MINIFICPP-974) Ensure that non-docker tested processors are not included into the make packaged docker builds
[ https://issues.apache.org/jira/browse/MINIFICPP-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896222#comment-16896222 ] Aldrin Piri commented on MINIFICPP-974: --- [~phrocker] I am in favor for of it. The complexity of libraries and functionality is large and has more inherent weight to inclusion to the codebase. If we do not have a way of conducting an automated way to cover the rudimentary aspects of it in the codebase, it will leave the codebase in a hard to maintain state. > Ensure that non-docker tested processors are not included into the make > packaged docker builds > -- > > Key: MINIFICPP-974 > URL: https://issues.apache.org/jira/browse/MINIFICPP-974 > Project: Apache NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Mr TheSegfault >Priority: Major > > This ensures that we don't trust and deploy artifacts that don't have some > type of regression test framework as it relates to our SITs. There may be > exceptions, so we can feel this desire out. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (MINIFICPP-793) Don't force reliance of RESTSender on flow SSLContext
[ https://issues.apache.org/jira/browse/MINIFICPP-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-793: -- Fix Version/s: 0.7.0 > Don't force reliance of RESTSender on flow SSLContext > -- > > Key: MINIFICPP-793 > URL: https://issues.apache.org/jira/browse/MINIFICPP-793 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (MINIFICPP-793) Don't force reliance of RESTSender on flow SSLContext
[ https://issues.apache.org/jira/browse/MINIFICPP-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-793. --- Resolution: Fixed > Don't force reliance of RESTSender on flow SSLContext > -- > > Key: MINIFICPP-793 > URL: https://issues.apache.org/jira/browse/MINIFICPP-793 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (MINIFICPP-961) Update Apache RAT to 0.13
[ https://issues.apache.org/jira/browse/MINIFICPP-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-961. --- Resolution: Fixed > Update Apache RAT to 0.13 > - > > Key: MINIFICPP-961 > URL: https://issues.apache.org/jira/browse/MINIFICPP-961 > Project: Apache NiFi MiNiFi C++ > Issue Type: Task >Affects Versions: 0.6.0 >Reporter: Aldrin Piri >Assignee: Arpad Boda >Priority: Trivial > Fix For: 0.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Apache RAT release a new version (0.13 - > https://creadur.apache.org/rat/download_rat.cgi) which precludes our linter > target from executing successfully. We should update to make the target > functional again. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (MINIFICPP-69) Capture enhanced build information in minifi.properties (C++)
[ https://issues.apache.org/jira/browse/MINIFICPP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-69. -- Resolution: Implemented > Capture enhanced build information in minifi.properties (C++) > - > > Key: MINIFICPP-69 > URL: https://issues.apache.org/jira/browse/MINIFICPP-69 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Aldrin Piri >Priority: Minor > > Work was done for NiFi (NIFI-2215) to expose additional information in the > About box. While we do not have a graphical view, capturing this information > in the minifi.properties file would be helpful for debugging and general > awareness of the system. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (MINIFICPP-903) cleanup root cmake
[ https://issues.apache.org/jira/browse/MINIFICPP-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-903. --- Resolution: Fixed > cleanup root cmake > -- > > Key: MINIFICPP-903 > URL: https://issues.apache.org/jira/browse/MINIFICPP-903 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This is an extension of MINIFICPP-570 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-923) Kafka version has performance issues and known bugs
[ https://issues.apache.org/jira/browse/MINIFICPP-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-923. --- Resolution: Fixed Fix Version/s: 0.7.0 > Kafka version has performance issues and known bugs > --- > > Key: MINIFICPP-923 > URL: https://issues.apache.org/jira/browse/MINIFICPP-923 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Should upgrade to 1.0.0 ( seems to be the most validated recently ) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-768) Change Trigger Logger in C2Agent from INFO -> DEBUG
[ https://issues.apache.org/jira/browse/MINIFICPP-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-768: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Change Trigger Logger in C2Agent from INFO -> DEBUG > --- > > Key: MINIFICPP-768 > URL: https://issues.apache.org/jira/browse/MINIFICPP-768 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.6.0 >Reporter: Jeremy Dyer >Assignee: Mr TheSegfault >Priority: Trivial > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently the C2Agent outputs a lot of messages when checking for triggers > that really should be part of a DEBUG and not INFO level logging -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-273) Assembly LICENSE has duplicate Querystring listings
Aldrin Piri created NIFIREG-273: --- Summary: Assembly LICENSE has duplicate Querystring listings Key: NIFIREG-273 URL: https://issues.apache.org/jira/browse/NIFIREG-273 Project: NiFi Registry Issue Type: Bug Affects Versions: 0.4.0 Reporter: Aldrin Piri Assignee: Aldrin Piri The LICENSE in the assembly has duplicate Querystring entries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-280) Move extension tests and test headers, lint extensions
[ https://issues.apache.org/jira/browse/MINIFICPP-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-280. --- Resolution: Fixed > Move extension tests and test headers, lint extensions > -- > > Key: MINIFICPP-280 > URL: https://issues.apache.org/jira/browse/MINIFICPP-280 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Caleb Johnson >Assignee: Caleb Johnson >Priority: Minor > Time Spent: 1h 20m > Remaining Estimate: 0h > > * 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 (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-837) Pass cmake arguments to make distro arguments
[ https://issues.apache.org/jira/browse/MINIFICPP-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-837. --- Resolution: Fixed Assignee: Mr TheSegfault > Pass cmake arguments to make distro arguments > - > > Key: MINIFICPP-837 > URL: https://issues.apache.org/jira/browse/MINIFICPP-837 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Pass cmake arguments to distro make commands. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6252) Stateful/Stateless relationship modeling is not listed as a dynamic property in UpdateAttribute
Aldrin Piri created NIFI-6252: - Summary: Stateful/Stateless relationship modeling is not listed as a dynamic property in UpdateAttribute Key: NIFI-6252 URL: https://issues.apache.org/jira/browse/NIFI-6252 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 1.9.0, 1.8.0, 1.7.0, 1.6.0, 1.5.0, 1.4.0, 1.3.0, 1.2.0 Reporter: Aldrin Piri NIFI-1582 provided the option to utilize state in UpdateAttribute but this was not annotated on the class such that it is documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6252) Stateful/Stateless relationship modeling is not listed as a dynamic relationship in UpdateAttribute
[ https://issues.apache.org/jira/browse/NIFI-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-6252: -- Summary: Stateful/Stateless relationship modeling is not listed as a dynamic relationship in UpdateAttribute (was: Stateful/Stateless relationship modeling is not listed as a dynamic property in UpdateAttribute) > Stateful/Stateless relationship modeling is not listed as a dynamic > relationship in UpdateAttribute > --- > > Key: NIFI-6252 > URL: https://issues.apache.org/jira/browse/NIFI-6252 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0 >Reporter: Aldrin Piri >Priority: Minor > Labels: newbie > > NIFI-1582 provided the option to utilize state in UpdateAttribute but this > was not annotated on the class such that it is documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-827) Install maven via bootstrap
[ https://issues.apache.org/jira/browse/MINIFICPP-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-827. --- Resolution: Fixed Fix Version/s: 0.7.0 > Install maven via bootstrap > --- > > Key: MINIFICPP-827 > URL: https://issues.apache.org/jira/browse/MINIFICPP-827 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Install maven via bootstrap and rely on it to build with jni -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-823) Change Build versions to 0.7.0
[ https://issues.apache.org/jira/browse/MINIFICPP-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-823. --- Resolution: Fixed Fix Version/s: 0.7.0 > Change Build versions to 0.7.0 > -- > > Key: MINIFICPP-823 > URL: https://issues.apache.org/jira/browse/MINIFICPP-823 > Project: Apache NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Change Build versions to 0.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-802) Allow packages with Python scripts
[ https://issues.apache.org/jira/browse/MINIFICPP-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-802. --- Resolution: Fixed Fix Version/s: 0.7.0 > Allow packages with Python scripts > -- > > Key: MINIFICPP-802 > URL: https://issues.apache.org/jira/browse/MINIFICPP-802 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-798) Maven verbosity causes Travis failures for JNI builds
[ https://issues.apache.org/jira/browse/MINIFICPP-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-798: -- Status: Patch Available (was: Open) > Maven verbosity causes Travis failures for JNI builds > - > > Key: MINIFICPP-798 > URL: https://issues.apache.org/jira/browse/MINIFICPP-798 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Due to the artifacts being downloaded, the generated output exceeds the > allowed log buffer in Travis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFICPP-798) Maven verbosity causes Travis failures for JNI builds
Aldrin Piri created MINIFICPP-798: - Summary: Maven verbosity causes Travis failures for JNI builds Key: MINIFICPP-798 URL: https://issues.apache.org/jira/browse/MINIFICPP-798 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.7.0 Due to the artifacts being downloaded, the generated output exceeds the allowed log buffer in Travis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-790) Integrate winflexbison for EL support in windows
[ https://issues.apache.org/jira/browse/MINIFICPP-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-790. --- Resolution: Fixed > Integrate winflexbison for EL support in windows > > > Key: MINIFICPP-790 > URL: https://issues.apache.org/jira/browse/MINIFICPP-790 > Project: NiFi MiNiFi C++ > Issue Type: Documentation > Environment: Windows >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Labels: Windows > Fix For: 0.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Been playing around with: > [https://github.com/lexxmark/winflexbison] > > Hopefully this will allow us to incorporate EL support into windows. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-791) Change to libressl v2.8.3
[ https://issues.apache.org/jira/browse/MINIFICPP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-791. --- Resolution: Fixed Fix Version/s: 0.7.0 > Change to libressl v2.8.3 > - > > Key: MINIFICPP-791 > URL: https://issues.apache.org/jira/browse/MINIFICPP-791 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Mr TheSegfault >Assignee: Mr TheSegfault >Priority: Major > Fix For: 0.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > It seems that libressl-portable's v2.9.0 tag references master for their > upgrade script. Not sure if this is intentional – but apparently v2.8.3 does > not. so we should switch to that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFICPP-794) Incorporate Flow File Expiration settings on connections from YAML definitions
Aldrin Piri created MINIFICPP-794: - Summary: Incorporate Flow File Expiration settings on connections from YAML definitions Key: MINIFICPP-794 URL: https://issues.apache.org/jira/browse/MINIFICPP-794 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri While the connection has the functionality to handle expiration settings, it does not appear this is currently interpreted/incorporated from a config file definition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
