[jira] [Updated] (HIVE-10339) Allow JDBC Driver to pass HTTP header Key/Value pairs

2016-04-08 Thread Thejas M Nair (JIRA)

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

Thejas M Nair updated HIVE-10339:
-
Release Note: Doc - 
https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-PassingHTTPHeaderKey/ValuePairsviaJDBCDriver

> Allow JDBC Driver to pass HTTP header Key/Value pairs
> -
>
> Key: HIVE-10339
> URL: https://issues.apache.org/jira/browse/HIVE-10339
> Project: Hive
>  Issue Type: Improvement
>  Components: Beeline
>Reporter: Hari Sankar Sivarama Subramaniyan
>Assignee: Hari Sankar Sivarama Subramaniyan
> Fix For: 1.2.0
>
> Attachments: HIVE-10339.1.patch, HIVE-10339.2.patch
>
>
> Currently Beeline & ODBC driver does not support carrying user specified HTTP 
> header.
> The beeline JDBC driver in HTTP mode connection string is as 
> jdbc:hive2://:/?hive.server2.transport.mode=http;hive.server2.thrift.http.path=,
> When transport mode is http Beeline/ODBC driver should allow end user to send 
> arbitrary HTTP Header name value pair.
> All the beeline driver needs to do is to use the user specified name values 
> and call the underlying HTTPClient API to set the header.
> E.g the Beeline connection string could be 
> jdbc:hive2://:/?hive.server2.transport.mode=http;hive.server2.thrift.http.path=,http.header.name1=value1,
> And the beeline will call underlying to set HTTP header to name1 and value1
> This is required for the  end user to send  identity in a HTTP header down to 
> Knox via beeline.



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


[jira] [Updated] (HIVE-10339) Allow JDBC Driver to pass HTTP header Key/Value pairs

2015-05-03 Thread Hari Sankar Sivarama Subramaniyan (JIRA)

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

Hari Sankar Sivarama Subramaniyan updated HIVE-10339:
-
Labels:   (was: TODOC1.2)

 Allow JDBC Driver to pass HTTP header Key/Value pairs
 -

 Key: HIVE-10339
 URL: https://issues.apache.org/jira/browse/HIVE-10339
 Project: Hive
  Issue Type: Improvement
  Components: Beeline
Reporter: Hari Sankar Sivarama Subramaniyan
Assignee: Hari Sankar Sivarama Subramaniyan
 Fix For: 1.2.0

 Attachments: HIVE-10339.1.patch, HIVE-10339.2.patch


 Currently Beeline  ODBC driver does not support carrying user specified HTTP 
 header.
 The beeline JDBC driver in HTTP mode connection string is as 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,
 When transport mode is http Beeline/ODBC driver should allow end user to send 
 arbitrary HTTP Header name value pair.
 All the beeline driver needs to do is to use the user specified name values 
 and call the underlying HTTPClient API to set the header.
 E.g the Beeline connection string could be 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,http.header.name1=value1,
 And the beeline will call underlying to set HTTP header to name1 and value1
 This is required for the  end user to send  identity in a HTTP header down to 
 Knox via beeline.



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


[jira] [Updated] (HIVE-10339) Allow JDBC Driver to pass HTTP header Key/Value pairs

2015-04-24 Thread Lefty Leverenz (JIRA)

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

Lefty Leverenz updated HIVE-10339:
--
Labels: TODOC1.2  (was: )

 Allow JDBC Driver to pass HTTP header Key/Value pairs
 -

 Key: HIVE-10339
 URL: https://issues.apache.org/jira/browse/HIVE-10339
 Project: Hive
  Issue Type: Improvement
  Components: Beeline
Reporter: Hari Sankar Sivarama Subramaniyan
Assignee: Hari Sankar Sivarama Subramaniyan
  Labels: TODOC1.2
 Fix For: 1.2.0

 Attachments: HIVE-10339.1.patch, HIVE-10339.2.patch


 Currently Beeline  ODBC driver does not support carrying user specified HTTP 
 header.
 The beeline JDBC driver in HTTP mode connection string is as 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,
 When transport mode is http Beeline/ODBC driver should allow end user to send 
 arbitrary HTTP Header name value pair.
 All the beeline driver needs to do is to use the user specified name values 
 and call the underlying HTTPClient API to set the header.
 E.g the Beeline connection string could be 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,http.header.name1=value1,
 And the beeline will call underlying to set HTTP header to name1 and value1
 This is required for the  end user to send  identity in a HTTP header down to 
 Knox via beeline.



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


[jira] [Updated] (HIVE-10339) Allow JDBC Driver to pass HTTP header Key/Value pairs

2015-04-21 Thread Hari Sankar Sivarama Subramaniyan (JIRA)

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

Hari Sankar Sivarama Subramaniyan updated HIVE-10339:
-
Attachment: HIVE-10339.2.patch

[~thejas] Addressed the review comments. Uploading patch #2

Thanks
Hari

 Allow JDBC Driver to pass HTTP header Key/Value pairs
 -

 Key: HIVE-10339
 URL: https://issues.apache.org/jira/browse/HIVE-10339
 Project: Hive
  Issue Type: Improvement
  Components: Beeline
Reporter: Hari Sankar Sivarama Subramaniyan
Assignee: Hari Sankar Sivarama Subramaniyan
 Attachments: HIVE-10339.1.patch, HIVE-10339.2.patch


 Currently Beeline  ODBC driver does not support carrying user specified HTTP 
 header.
 The beeline JDBC driver in HTTP mode connection string is as 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,
 When transport mode is http Beeline/ODBC driver should allow end user to send 
 arbitrary HTTP Header name value pair.
 All the beeline driver needs to do is to use the user specified name values 
 and call the underlying HTTPClient API to set the header.
 E.g the Beeline connection string could be 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,http.header.name1=value1,
 And the beeline will call underlying to set HTTP header to name1 and value1
 This is required for the  end user to send  identity in a HTTP header down to 
 Knox via beeline.



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


[jira] [Updated] (HIVE-10339) Allow JDBC Driver to pass HTTP header Key/Value pairs

2015-04-14 Thread Hari Sankar Sivarama Subramaniyan (JIRA)

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

Hari Sankar Sivarama Subramaniyan updated HIVE-10339:
-
Attachment: HIVE-10339.1.patch

 Allow JDBC Driver to pass HTTP header Key/Value pairs
 -

 Key: HIVE-10339
 URL: https://issues.apache.org/jira/browse/HIVE-10339
 Project: Hive
  Issue Type: Improvement
  Components: Beeline
Reporter: Hari Sankar Sivarama Subramaniyan
Assignee: Hari Sankar Sivarama Subramaniyan
 Attachments: HIVE-10339.1.patch


 Currently Beeline  ODBC driver does not support carrying user specified HTTP 
 header.
 The beeline JDBC driver in HTTP mode connection string is as 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,
 When transport mode is http Beeline/ODBC driver should allow end user to send 
 arbitrary HTTP Header name value pair.
 All the beeline driver needs to do is to use the user specified name values 
 and call the underlying HTTPClient API to set the header.
 E.g the Beeline connection string could be 
 jdbc:hive2://host:port/db?hive.server2.transport.mode=http;hive.server2.thrift.http.path=http_endpoint,http.header.name1=value1,
 And the beeline will call underlying to set HTTP header to name1 and value1
 This is required for the  end user to send  identity in a HTTP header down to 
 Knox via beeline.



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