[jira] [Resolved] (CALCITE-1471) HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows

2016-10-26 Thread Julian Hyde (JIRA)

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

Julian Hyde resolved CALCITE-1471.
--
Resolution: Fixed

Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/08eb16bb; thanks 
for the PR, [~mihalik]!

> HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows
> -
>
> Key: CALCITE-1471
> URL: https://issues.apache.org/jira/browse/CALCITE-1471
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Affects Versions: avatica-1.8.0
>Reporter: Julian Hyde
> Fix For: avatica-1.9.0
>
>
> The test {{HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed}} 
> fails on Windows, with the following message:
> {noformat}
> Failed tests:
>   HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed:223 
> expected:<[OK cli...@example.com]> but was:<[
> 
> 
> Error 500 
> 
> 
> HTTP ERROR: 500
> Problem accessing /. Reason:
> Unauthenticated users should not reach here!
> Powered by Jetty://
> 
> 
> ]>
> {noformat}
> Unlike some other SPNEGO tests, this one occurs every time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CALCITE-1471) HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows

2016-10-26 Thread Julian Hyde (JIRA)

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

Julian Hyde updated CALCITE-1471:
-
Fix Version/s: avatica-1.9.0

> HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows
> -
>
> Key: CALCITE-1471
> URL: https://issues.apache.org/jira/browse/CALCITE-1471
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Affects Versions: avatica-1.8.0
>Reporter: Julian Hyde
> Fix For: avatica-1.9.0
>
>
> The test {{HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed}} 
> fails on Windows, with the following message:
> {noformat}
> Failed tests:
>   HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed:223 
> expected:<[OK cli...@example.com]> but was:<[
> 
> 
> Error 500 
> 
> 
> HTTP ERROR: 500
> Problem accessing /. Reason:
> Unauthenticated users should not reach here!
> Powered by Jetty://
> 
> 
> ]>
> {noformat}
> Unlike some other SPNEGO tests, this one occurs every time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CALCITE-1471) HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows

2016-10-26 Thread Julian Hyde (JIRA)

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

Julian Hyde updated CALCITE-1471:
-
Affects Version/s: avatica-1.8.0

> HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows
> -
>
> Key: CALCITE-1471
> URL: https://issues.apache.org/jira/browse/CALCITE-1471
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Affects Versions: avatica-1.8.0
>Reporter: Julian Hyde
>
> The test {{HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed}} 
> fails on Windows, with the following message:
> {noformat}
> Failed tests:
>   HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed:223 
> expected:<[OK cli...@example.com]> but was:<[
> 
> 
> Error 500 
> 
> 
> HTTP ERROR: 500
> Problem accessing /. Reason:
> Unauthenticated users should not reach here!
> Powered by Jetty://
> 
> 
> ]>
> {noformat}
> Unlike some other SPNEGO tests, this one occurs every time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CALCITE-1471) HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows

2016-10-26 Thread Julian Hyde (JIRA)
Julian Hyde created CALCITE-1471:


 Summary: 
HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed fails on Windows
 Key: CALCITE-1471
 URL: https://issues.apache.org/jira/browse/CALCITE-1471
 Project: Calcite
  Issue Type: Bug
  Components: avatica
Reporter: Julian Hyde


The test {{HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed}} fails 
on Windows, with the following message:

{noformat}
Failed tests:
  HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed:223 
expected:<[OK cli...@example.com]> but was:<[


Error 500 


HTTP ERROR: 500
Problem accessing /. Reason:
Unauthenticated users should not reach here!
Powered by Jetty://


]>
{noformat}

Unlike some other SPNEGO tests, this one occurs every time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CALCITE-1470) HttpServerSpnegoWithJaasTest fails on Windows

2016-10-26 Thread Josh Elser (JIRA)
Josh Elser created CALCITE-1470:
---

 Summary: HttpServerSpnegoWithJaasTest fails on Windows
 Key: CALCITE-1470
 URL: https://issues.apache.org/jira/browse/CALCITE-1470
 Project: Calcite
  Issue Type: Bug
  Components: avatica
Reporter: Josh Elser
Assignee: Aaron Mihalik
 Fix For: avatica-1.10.0


{noformat}
Failed tests:
  HttpServerSpnegoWithJaasTest.testAuthenticatedClientsAllowed:223
expected:<[OK cli...@example.com]> but was:<[


Error 500 


HTTP ERROR: 500
Problem accessing /. Reason:
Unauthenticated users should not reach here!
Powered by Jetty://


]>

A related error may be:
GSSException: Failure unspecified at GSS-API level (Mechanism level:
Invalid argument (400) - Cannot find key of appropriate type to decrypt AP
REP - AES128 CTS mode with HMAC SHA1-96)
at
sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:856)
at
sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:342)
{noformat}

{noformat}
The key line in the debug out was the "Found KeyTab" line below:

SpNegoContext.initSecContext: sending token of type = SPNEGO NegTokenInit
SNegoContext.initSecContext: sending token = a0 82 ...
Found KeyTab C:Users mihalik empcalcite vaticaserver
argetHttpServerSpnegoWithJaasTest_keytabsHTTP_localhost.keytab
for HTTP/localh...@example.com
Entered SpNegoContext.acceptSecContext with state=STATE_NEW
SpNegoContext.acceptSecContext: receiving token = a0 82 ...
SpNegoToken NegTokenInit: reading Mechanism Oid = 1.2.840.113554.1.2.2
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CALCITE-1469) QueryServer trims Char type padded spaces

2016-10-26 Thread Josh Elser (JIRA)

[ 
https://issues.apache.org/jira/browse/CALCITE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608928#comment-15608928
 ] 

Josh Elser commented on CALCITE-1469:
-

Tagged this one as affectsVersion=1.6.0 (I think that's what we shipped in 
Phoenix 4.5.2). Any help in writing a test to verify what Avatica is doing 
would be a great first step.

> QueryServer trims Char type padded spaces
> -
>
> Key: CALCITE-1469
> URL: https://issues.apache.org/jira/browse/CALCITE-1469
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Affects Versions: 1.6.0
> Environment: HDP2.3
> Phoenix4.5.2
>Reporter: Hai Fu Yu
>Assignee: Josh Elser
>Priority: Minor
>
> Query server is trimming padded spaces on Char type data and it convert back 
> to fixed length in the client side. 
> This is unexpected to us as common database would likely return fixed-length 
> data in fixed length. Is this intentional for reducing network traffic? It 
> would be great if we could disable auto-trimming on the queryServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CALCITE-1469) QueryServer trims Char type padded spaces

2016-10-26 Thread Josh Elser (JIRA)

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

Josh Elser updated CALCITE-1469:

Affects Version/s: 1.6.0

> QueryServer trims Char type padded spaces
> -
>
> Key: CALCITE-1469
> URL: https://issues.apache.org/jira/browse/CALCITE-1469
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Affects Versions: 1.6.0
> Environment: HDP2.3
> Phoenix4.5.2
>Reporter: Hai Fu Yu
>Assignee: Josh Elser
>Priority: Minor
>
> Query server is trimming padded spaces on Char type data and it convert back 
> to fixed length in the client side. 
> This is unexpected to us as common database would likely return fixed-length 
> data in fixed length. Is this intentional for reducing network traffic? It 
> would be great if we could disable auto-trimming on the queryServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Moved] (CALCITE-1469) QueryServer trims Char type padded spaces

2016-10-26 Thread Josh Elser (JIRA)

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

Josh Elser moved PHOENIX-2322 to CALCITE-1469:
--

Affects Version/s: (was: 4.5.2)
 Workflow: jira  (was: no-reopen-closed, patch-avail)
   Issue Type: Bug  (was: Improvement)
  Key: CALCITE-1469  (was: PHOENIX-2322)
  Project: Calcite  (was: Phoenix)

> QueryServer trims Char type padded spaces
> -
>
> Key: CALCITE-1469
> URL: https://issues.apache.org/jira/browse/CALCITE-1469
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
> Environment: HDP2.3
> Phoenix4.5.2
>Reporter: Hai Fu Yu
>Assignee: Josh Elser
>Priority: Minor
>
> Query server is trimming padded spaces on Char type data and it convert back 
> to fixed length in the client side. 
> This is unexpected to us as common database would likely return fixed-length 
> data in fixed length. Is this intentional for reducing network traffic? It 
> would be great if we could disable auto-trimming on the queryServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CALCITE-1469) QueryServer trims Char type padded spaces

2016-10-26 Thread Josh Elser (JIRA)

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

Josh Elser updated CALCITE-1469:

Component/s: avatica

> QueryServer trims Char type padded spaces
> -
>
> Key: CALCITE-1469
> URL: https://issues.apache.org/jira/browse/CALCITE-1469
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Affects Versions: 1.6.0
> Environment: HDP2.3
> Phoenix4.5.2
>Reporter: Hai Fu Yu
>Assignee: Josh Elser
>Priority: Minor
>
> Query server is trimming padded spaces on Char type data and it convert back 
> to fixed length in the client side. 
> This is unexpected to us as common database would likely return fixed-length 
> data in fixed length. Is this intentional for reducing network traffic? It 
> would be great if we could disable auto-trimming on the queryServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)