Jenkins build is back to normal : Knox-master-patch-scan #80039

2018-06-08 Thread Apache Jenkins Server 
See

Build failed in Jenkins: Knox-master-patch-scan #80038

2018-06-08 Thread Apache Jenkins Server 
See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H17 (Hadoop xenial) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/knox.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 0e34aa16c86b619a1400ca589408f94f0728497d 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0e34aa16c86b619a1400ca589408f94f0728497d
Commit message: "KNOX-1349 - Fix Knox versioning for service defs. (UnitTest to 
be followed in next commit)"
 > git rev-list --no-walk 0e34aa16c86b619a1400ca589408f94f0728497d # timeout=10
[Knox-master-patch-scan] $ /bin/bash /tmp/jenkins8258524464740856937.sh
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 
 231k0  231k0 0   161k  0 --:--:--  0:00:01 --:--:--  161k
curl: (56) GnuTLS recv error (-110): The TLS connection was non-properly 
terminated.
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Commented] (KNOX-1349) When multiple versions of service defs are specified Knox does not pick the greatest

2018-06-08 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on KNOX-1349:
---

Commit 0e34aa16c86b619a1400ca589408f94f0728497d in knox's branch 
refs/heads/master from [~moresandeep]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=0e34aa1 ]

KNOX-1349 - Fix Knox versioning for service defs. (UnitTest to be followed in 
next commit)


> When multiple versions of service defs are specified Knox does not pick the 
> greatest
> 
>
> Key: KNOX-1349
> URL: https://issues.apache.org/jira/browse/KNOX-1349
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Sandeep More
>Assignee: Sandeep More
>Priority: Major
> Fix For: 1.1.0
>
>
> When there are multiple versions of service defs. specified Knox should 
> always pick the service with the greater version. This functionality seems to 
> be broken (or missing). 



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

[jira] [Created] (KNOX-1349) When multiple versions of service defs are specified Knox does not pick the greatest

2018-06-08 Thread Sandeep More (JIRA) 
Sandeep More created KNOX-1349:
--

 Summary: When multiple versions of service defs are specified Knox 
does not pick the greatest
 Key: KNOX-1349
 URL: https://issues.apache.org/jira/browse/KNOX-1349
 Project: Apache Knox
  Issue Type: Bug
  Components: Server
Reporter: Sandeep More
Assignee: Sandeep More
 Fix For: 1.1.0


When there are multiple versions of service defs. specified Knox should always 
pick the service with the greater version. This functionality seems to be 
broken (or missing). 



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

[jira] [Commented] (KNOX-1237) Knox DSL should support HBase Stateless Scanner

2018-06-08 Thread Dequan Chen (JIRA) 


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

Dequan Chen commented on KNOX-1237:
---

To [~pzampino],

How are you?

I have recently implemented the Knox shell HBase stateless scanner and it 
passed all the tests against our enterprise HDP-included HBase (v1.1.2). I am 
wondering if I provide the patch in the coming future, can it be integrated to 
the Knox-1.1.0 release or not?

Dequan Chen

6/8/2018 2:35pm

> Knox DSL should support HBase Stateless Scanner
> ---
>
> Key: KNOX-1237
> URL: https://issues.apache.org/jira/browse/KNOX-1237
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: ClientDSL
>Reporter: Kevin Risden
>Priority: Minor
> Fix For: 1.2.0
>
>
> KNOX-8 added support for HBase REST apis via Knox. The Knox DSL supports 
> stateful scanners as shown in the documentation 
> (https://knox.apache.org/books/knox-1-0-0/user-guide.html#table(String+tableName).scanner().create()+-+Scanner+Creation).
> HBase REST supports stateless scanners 
> ([https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/rest/package-summary.html#operation_stateless_scanner])
>  which can be easily load balanced. The feature is not well documented in 
> HBase REST.
> Currently if using stateful scanners and Knox or HBase REST is being load 
> balanced, there will be an issue using that scanner. The stateless scanners 
> avoid this since they have all the information necessary.



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

[jira] [Resolved] (KNOX-1348) Provider Configuration Wizard HA Provider Validation for ZooKeeper Ensemble is Wrong

2018-06-08 Thread Phil Zampino (JIRA) 


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

Phil Zampino resolved KNOX-1348.

Resolution: Fixed

> Provider Configuration Wizard HA Provider Validation for ZooKeeper Ensemble 
> is Wrong
> 
>
> Key: KNOX-1348
> URL: https://issues.apache.org/jira/browse/KNOX-1348
> Project: Apache Knox
>  Issue Type: Bug
>  Components: AdminUI
>Affects Versions: 1.1.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
>Priority: Major
> Fix For: 1.1.0
>
>
> The validation regular expression for HA provider zookeeperEnsemble values 
> mistakenly checks for a semicolon delimiter instead of a comma.



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

[jira] [Commented] (KNOX-1348) Provider Configuration Wizard HA Provider Validation for ZooKeeper Ensemble is Wrong

2018-06-08 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on KNOX-1348:
---

Commit 055ec2a7cacc3c961b377d047bd8230022b31a8a in knox's branch 
refs/heads/master from [~pzamp...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=055ec2a ]

KNOX-1348 - Provider Configuration Wizard HA Provider Validation for ZooKeeper 
Ensemble is Wrong


> Provider Configuration Wizard HA Provider Validation for ZooKeeper Ensemble 
> is Wrong
> 
>
> Key: KNOX-1348
> URL: https://issues.apache.org/jira/browse/KNOX-1348
> Project: Apache Knox
>  Issue Type: Bug
>  Components: AdminUI
>Affects Versions: 1.1.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
>Priority: Major
> Fix For: 1.1.0
>
>
> The validation regular expression for HA provider zookeeperEnsemble values 
> mistakenly checks for a semicolon delimiter instead of a comma.



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

[jira] [Created] (KNOX-1348) Provider Configuration Wizard HA Provider Validation for ZooKeeper Ensemble is Wrong

2018-06-08 Thread Phil Zampino (JIRA) 
Phil Zampino created KNOX-1348:
--

 Summary: Provider Configuration Wizard HA Provider Validation for 
ZooKeeper Ensemble is Wrong
 Key: KNOX-1348
 URL: https://issues.apache.org/jira/browse/KNOX-1348
 Project: Apache Knox
  Issue Type: Bug
  Components: AdminUI
Affects Versions: 1.1.0
Reporter: Phil Zampino
Assignee: Phil Zampino
 Fix For: 1.1.0


The validation regular expression for HA provider zookeeperEnsemble values 
mistakenly checks for a semicolon delimiter instead of a comma.



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

[jira] [Resolved] (KNOX-1347) X-Forwarded-Context header is not rewritten correctly

2018-06-08 Thread Larry McCay (JIRA) 


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

Larry McCay resolved KNOX-1347.
---
Resolution: Fixed

[~mgaido] - I have just committed this to master and it will be available in 
the upcoming 1.1.0 release. Thank you for this contribution to Apache Knox!

> X-Forwarded-Context header is not rewritten correctly
> -
>
> Key: KNOX-1347
> URL: https://issues.apache.org/jira/browse/KNOX-1347
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Marco Gaido
>Assignee: Marco Gaido
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: KNOX-1347.patch
>
>
> In KNOX-1295 a rewrite rule for properly having the X-Forwarded-Context full 
> path was introduced. Unfortunately, there are 2 problems with the current 
> rewrite rule:
>  - It should add {{sparkhistory}}, but instead it adds {{sparkhistoryui}};
>  - It trims the leading {{/}}, so {{/gateway/default}} becomes 
> {{gateway/default/sparkhistoryui}};



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

[jira] [Updated] (KNOX-1347) X-Forwarded-Context header is not rewritten correctly

2018-06-08 Thread Larry McCay (JIRA) 


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

Larry McCay updated KNOX-1347:
--
Fix Version/s: 1.1.0

> X-Forwarded-Context header is not rewritten correctly
> -
>
> Key: KNOX-1347
> URL: https://issues.apache.org/jira/browse/KNOX-1347
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Marco Gaido
>Assignee: Marco Gaido
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: KNOX-1347.patch
>
>
> In KNOX-1295 a rewrite rule for properly having the X-Forwarded-Context full 
> path was introduced. Unfortunately, there are 2 problems with the current 
> rewrite rule:
>  - It should add {{sparkhistory}}, but instead it adds {{sparkhistoryui}};
>  - It trims the leading {{/}}, so {{/gateway/default}} becomes 
> {{gateway/default/sparkhistoryui}};



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

[jira] [Commented] (KNOX-1347) X-Forwarded-Context header is not rewritten correctly

2018-06-08 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on KNOX-1347:
---

Commit af682ac82cd46e8c28a2c38d4aed7bb5af2fb60d in knox's branch 
refs/heads/master from [~lmc...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=af682ac ]

KNOX-1347 - X-Forwarded-Context header is not rewritten correctly


> X-Forwarded-Context header is not rewritten correctly
> -
>
> Key: KNOX-1347
> URL: https://issues.apache.org/jira/browse/KNOX-1347
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Marco Gaido
>Assignee: Marco Gaido
>Priority: Major
> Attachments: KNOX-1347.patch
>
>
> In KNOX-1295 a rewrite rule for properly having the X-Forwarded-Context full 
> path was introduced. Unfortunately, there are 2 problems with the current 
> rewrite rule:
>  - It should add {{sparkhistory}}, but instead it adds {{sparkhistoryui}};
>  - It trims the leading {{/}}, so {{/gateway/default}} becomes 
> {{gateway/default/sparkhistoryui}};



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

[jira] [Assigned] (KNOX-1347) X-Forwarded-Context header is not rewritten correctly

2018-06-08 Thread Larry McCay (JIRA) 


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

Larry McCay reassigned KNOX-1347:
-

Assignee: Marco Gaido

> X-Forwarded-Context header is not rewritten correctly
> -
>
> Key: KNOX-1347
> URL: https://issues.apache.org/jira/browse/KNOX-1347
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Marco Gaido
>Assignee: Marco Gaido
>Priority: Major
> Attachments: KNOX-1347.patch
>
>
> In KNOX-1295 a rewrite rule for properly having the X-Forwarded-Context full 
> path was introduced. Unfortunately, there are 2 problems with the current 
> rewrite rule:
>  - It should add {{sparkhistory}}, but instead it adds {{sparkhistoryui}};
>  - It trims the leading {{/}}, so {{/gateway/default}} becomes 
> {{gateway/default/sparkhistoryui}};



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

[jira] [Updated] (KNOX-1347) X-Forwarded-Context header is not rewritten correctly

2018-06-08 Thread Marco Gaido (JIRA) 


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

Marco Gaido updated KNOX-1347:
--
Attachment: KNOX-1347.patch

> X-Forwarded-Context header is not rewritten correctly
> -
>
> Key: KNOX-1347
> URL: https://issues.apache.org/jira/browse/KNOX-1347
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Marco Gaido
>Priority: Major
> Attachments: KNOX-1347.patch
>
>
> In KNOX-1295 a rewrite rule for properly having the X-Forwarded-Context full 
> path was introduced. Unfortunately, there are 2 problems with the current 
> rewrite rule:
>  - It should add {{sparkhistory}}, but instead it adds {{sparkhistoryui}};
>  - It trims the leading {{/}}, so {{/gateway/default}} becomes 
> {{gateway/default/sparkhistoryui}};



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

[jira] [Created] (KNOX-1347) X-Forwarded-Context header is not rewritten correctly

2018-06-08 Thread Marco Gaido (JIRA) 
Marco Gaido created KNOX-1347:
-

 Summary: X-Forwarded-Context header is not rewritten correctly
 Key: KNOX-1347
 URL: https://issues.apache.org/jira/browse/KNOX-1347
 Project: Apache Knox
  Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Marco Gaido


In KNOX-1295 a rewrite rule for properly having the X-Forwarded-Context full 
path was introduced. Unfortunately, there are 2 problems with the current 
rewrite rule:
 - It should add {{sparkhistory}}, but instead it adds {{sparkhistoryui}};
 - It trims the leading {{/}}, so {{/gateway/default}} becomes 
{{gateway/default/sparkhistoryui}};




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