[jira] [Commented] (KUDU-947) Improve documentation on how to construct various C++ client classes

2017-04-05 Thread Grant Henke (JIRA)

[ 
https://issues.apache.org/jira/browse/KUDU-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956950#comment-15956950
 ] 

Grant Henke commented on KUDU-947:
--

I also ran into this a bit with KuduTable->partition_schema(). This returns the 
kudu common PartitionSchema which has a lot of methods that appear to be 
"internal usage only" since they use the Schema class instead of KuduSchema.

> Improve documentation on how to construct various C++ client classes
> 
>
> Key: KUDU-947
> URL: https://issues.apache.org/jira/browse/KUDU-947
> Project: Kudu
>  Issue Type: Bug
>  Components: client
>Affects Versions: Public beta
>Reporter: Mike Percy
>
> Having some issues with the client API:
> * There doesn't seem to be a way to get a KuduSchema from a Schema, since 
> that constructor is private
> * In order to encode my splits, I need to use KuduPartialRow::EncodeKey() 
> according to the header comments in the table builder, but KuduPartialRow is 
> only constructible with a Schema.
> Does this mean clients are expected to use both KuduSchema and Schema when 
> creating tables?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (KUDU-1965) Allow user provided TLS certificates to work with KRPC

2017-04-05 Thread Sailesh Mukil (JIRA)
Sailesh Mukil created KUDU-1965:
---

 Summary: Allow user provided TLS certificates to work with KRPC
 Key: KUDU-1965
 URL: https://issues.apache.org/jira/browse/KUDU-1965
 Project: Kudu
  Issue Type: Bug
  Components: rpc, security
Affects Versions: 1.3.0
Reporter: Sailesh Mukil
Assignee: Sailesh Mukil


Kudu generates certificates when TLS is enabled and if the user does not 
provide them. These certificates have Kudu specific encodings which are checked 
for in the RPC negotiation phase.

If the certificates are user provided, it's highly likely that they will not 
contain these encodings, thus causing the certificate negotiation phase to fail.

We can check for and verify these encodings if the certificates are provided by 
Kudu, else we can skip that step in the negotiation phase if the certificates 
are user provided.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)