New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NIFI-6647 - Upgrading Apache Ignite version to 2.8.0 #3720
Conversation
@jtstorck could you please review this by any chance? Saw you had other PRs related to Apache Ignite. |
@matthew-formosa-gig can you find out what is creating Untracked files: It should create directories under target so it is cleanly handled during the build process and properly ignored in terms of source/etc.. otherwise this looks ready to roll. I could build fine on java8 and java 11 and the travis issues weren't related to this PR so otherwise it is ready |
@matthew-formosa-gig the ignite folks leave a quite nice readme in there This is Apache Ignite working directory that contains information that You can change the location of working directory with |
Thanks for your feedback. Successfully redirected work directory to target folder. |
@joewitt Kind reminder with regards to this PR. |
@joewitt It's been a while :) Upgraded to Apache Ignite 2.8.0. Tests are successful locally, not sure why some seem to be failing on ci-workflow. |
#4278 includes this change. |
Description of PR
The version of Apache Ignite is currently set to 1.6.0 which is now over 3 years old. Upgrading to the latest version, that is 2.8.0.
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically
master
)?Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not
squash
or use--force
when pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean install
at the rootnifi
folder?