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-6032 - CDC for Oracle using xstream #3887
Conversation
Eagerly waiting for this feature 👍 |
@shivamkh90 - that would greatly help if you can checkout this pull request, give it a try and report your results here. An extensive set of tests with your flow definitions and screenshots of the results and expectations would help others to also chime in. We have tons of PR and we need help from the community to get the PRs merged into NiFi. |
@rkarthik29 Thanks for creating this PR! |
@rkarthik29
So I had to copy the nars from nifi-1/nifi-nar-bundles/nifi-oraclecdc-bundle to the nifi-1.11.0-SNAPSHOT/lib directory manually. Please, check the parent pom.xml. |
There is a profile config in the nifi parent pom.xml. Please add -p include-oraclecdc to maven command to package this piece as part of nifi tar. include-oraclecdc false org.apache.nifi nifi-oraclecdc-nar 1.11.0-SNAPSHOT nar org.apache.nifi nifi-oraclecdcservice-api-nar 1.11.0-SNAPSHOT nar |
Hi @rkarthik29 I am getting the following error: Steps that I did: BUILD NIFI
INSTALL ORACLE DRIVER
CONFIG LIBS
CREATE ORACLE XSTREAM OUTBOUND SERVER
NiFi Processor: NiFi Services: Oracle views: NiFi log:
Is something wrong? |
looks like there is an issue with getConnection(). is it probably timing out???? this is the error log o.a.n.controller.StandardProcessorNode Timed out while waiting for OnScheduled of OracleChangeCapture[id=32c99420-0175-1000-0e97-840ff38cca51] to finish. An attempt is made to cancel the task via Thread.interrupt(). However it does not guarantee that the task will be canceled since the code inside current OnScheduled operation may have been written to ignore interrupts which may result in a runaway thread. This could lead to more issues, eventually requiring NiFi to be restarted. This is usually a bug in the target Processor 'OracleChangeCapture[id=32c99420-0175-1000-0e97-840ff38cca51]' that needs to be documented, reported and eventually fixed. that error seems to come from DBCPConectionPool. Best way to figure out is to run the ITOracleChangeCaptureTest via eclipse,you can then put a breakpoint in standardoraclecdcservice.attach() to get more details on why this is happening. This is probably needs to be handled.. https://issues.apache.org/jira/browse/DBCP-459. You have to investigate why that timeout is happening though. Make sure you are using a thick client for connection to oracle. I don't think that is the cause of this error, but ensure that you are doing that. Karthik |
@davyam Karthik |
Hi @rkarthik29 The instructions that I followed were almost the same, but I will try again following yours. About the libraries, they are defined in bootstrap.conf, I just forget to show you in my previous comment. Thanks for the quick answers. Davy Machado |
Hi @rkarthik29 I got it! It is working! I think that the problem was the StandardOracleClassLoaderService config. I changed the value of Database Driver Location(s) to /usr/lib/oracle/12.2/client64/lib, instead of the jar path. Now I will do more tests. Thanks! Davy Machado |
We're marking this PR as stale due to lack of updates in the past few months. If after another couple of weeks the stale label has not been removed this PR will be closed. This stale marker and eventual auto close does not indicate a judgement of the PR just lack of reviewer bandwidth and helps us keep the PR queue more manageable. If you would like this PR re-opened you can do so and a committer can remove the stale tag. Or you can open a new PR. Try to help review other PRs to increase PR review bandwidth which in turn helps yours. |
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-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?LICENSE
file, including the mainLICENSE
file undernifi-assembly
?NOTICE
file, including the mainNOTICE
file found undernifi-assembly
?.displayName
in addition to .name (programmatic access) for each of the new properties?For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.