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

ASF GitHub Bot commented on NIFI-5054:
--------------------------------------

Github user mgroves commented on the issue:

    https://github.com/apache/nifi/pull/2750
  
    Hi @ijokarumawak I tried building this today (on Windows). I'm not much of 
a Java developer, so this could easily be a noob mistake. It looks like there 
was an error here:
    
    ```
    > [ERROR] Errors: 
    > [ERROR]   
TestMinimalLockingWriteAheadLog.testRecoverFileThatHasTrailingNULBytesAndTruncation:503
 ╗ OverlappingFileLock
    > [INFO] 
    > [ERROR] Tests run: 30, Failures: 0, Errors: 1, Skipped: 3
    > 
    ```
    
    Which leads to a build failure at the end:
    
    ```
    > [INFO] 
------------------------------------------------------------------------
    > [INFO] BUILD FAILURE
    > [INFO] 
------------------------------------------------------------------------
    > [INFO] Total time: 01:38 min
    > [INFO] Finished at: 2018-06-04T11:44:56-07:00
    > [INFO] Final Memory: 134M/920M
    > [INFO] 
------------------------------------------------------------------------
    > [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project nifi-write-ahead-log: There are test failures.
    > [ERROR] 
    > [ERROR] Please refer to 
C:\zproj\nifi-ijokarumawak\nifi-commons\nifi-write-ahead-log\target\surefire-reports
 for the individual test results.
    > [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
    > [ERROR] -> [Help 1]
    > [ERROR] 
    > [ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.
    > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    > [ERROR] 
    > [ERROR] For more information about the errors and possible solutions, 
please read the following articles:
    > [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
    > [ERROR] 
    > [ERROR] After correcting the problems, you can resume the build with the 
command
    > [ERROR]   mvn <goals> -rf :nifi-write-ahead-log
    ```
    
    I've put the entire output into a pastebin here: 
https://pastebin.com/Am3k3xn4
    Is there something I'm missing or doing wrong?



> Nifi Couchbase Processors does not support User Authentication
> --------------------------------------------------------------
>
>                 Key: NIFI-5054
>                 URL: https://issues.apache.org/jira/browse/NIFI-5054
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Shagun Jaju
>            Assignee: Koji Kawamura
>            Priority: Major
>              Labels: authentication, security
>
> Issue Description: Nifi Couchbase processors don't work with new couchbase 
> versions 5.0 and 5.1.
> New Couchbase Version 5.x has introduced *Role Based Access Control (RBAC),* 
> a ** new security feature.
>  # All buckets must now be accessed by a *user*/*password* combination that 
> has a *role with access rights* to the bucket.
>  # Buckets no longer use bucket-level passwords
>  # There is no default bucket and no sample buckets with blank passwords.
>  # You cannot create a user without a password.
> *(Ref:* 
> https://developer.couchbase.com/documentation/server/5.0/introduction/whats-new.html
> [https://blog.couchbase.com/new-sdk-authentication/] )
>  
> nifi-couchbase-processors : GetCouchbaseKey and PutCouchbaseKey using 
> Controller Service still uses old authentication mechanism.
>  * org.apache.nifi.processors.couchbase.GetCouchbaseKey
>  * org.apache.nifi.processors.couchbase.PutCouchbaseKey
> Ref: 
> [https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-couchbase-bundle/nifi-couchbase-processors/src/main/java/org/apache/nifi/couchbase/CouchbaseClusterService.java#L116]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to