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

Sudheesh Katkam updated DRILL-2365:
-----------------------------------
    Description: 
git.commit.id.abbrev=a84f7b9

When querying for BOOT options, we get null for 'kind' for many of these 
options:
{code}
+------------+------------+------------+------------+------------+------------+------------+
 
|    name    |    kind    |    type    |  num_val   | string_val |  bool_val  | 
float_val  | 
+------------+------------+------------+------------+------------+------------+------------+
 
| drill.exec.buffer.impl | null       | BOOT       | null       | 
"org.apache.drill.exec.work.batch.UnlimitedRawBatchBuffer" | null       | null  
     |                                                            
| drill.exec.buffer.size | null       | BOOT       | null       | "6"        | 
null       | null       |  
| drill.exec.cluster-id | null       | BOOT       | null       | 
"cluster105-drillbits" | null       | null       |
{code}
In contrast, for other options, we get meaningful values for 'kind':
{code}
0: jdbc:drill:> select * from sys.options where type = 'BOOT' and kind is not 
null order by name;         
+------------+------------+------------+------------+------------+------------+------------+
              
|    name    |    kind    |    type    |  num_val   | string_val |  bool_val  | 
float_val  |              
+------------+------------+------------+------------+------------+------------+------------+
              
| drill.client.supports-complex-types | BOOLEAN    | BOOT       | null       | 
null       | true       | null       |
{code}
It appears to make sense to have the right values for the 'kind' column.

  was:
git.commit.id.abbrev=a84f7b9

When querying for BOOT options, we get null for 'kind' for many of these 
options:

+------------+------------+------------+------------+------------+------------+------------+
 
|    name    |    kind    |    type    |  num_val   | string_val |  bool_val  | 
float_val  | 
+------------+------------+------------+------------+------------+------------+------------+
 
| drill.exec.buffer.impl | null       | BOOT       | null       | 
"org.apache.drill.exec.work.batch.UnlimitedRawBatchBuffer" | null       | null  
     |                                                            
| drill.exec.buffer.size | null       | BOOT       | null       | "6"        | 
null       | null       |  
| drill.exec.cluster-id | null       | BOOT       | null       | 
"cluster105-drillbits" | null       | null       |

In contrast, for other options, we get meaningful values for 'kind':

0: jdbc:drill:> select * from sys.options where type = 'BOOT' and kind is not 
null order by name;         
+------------+------------+------------+------------+------------+------------+------------+
              
|    name    |    kind    |    type    |  num_val   | string_val |  bool_val  | 
float_val  |              
+------------+------------+------------+------------+------------+------------+------------+
              
| drill.client.supports-complex-types | BOOLEAN    | BOOT       | null       | 
null       | true       | null       |

It appears to make sense to have the right values for the 'kind' column.


> populate values for 'kind' for sys.options with type == 'BOOT'
> --------------------------------------------------------------
>
>                 Key: DRILL-2365
>                 URL: https://issues.apache.org/jira/browse/DRILL-2365
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Metadata
>            Reporter: Zhiyong Liu
>            Assignee: Steven Phillips
>            Priority: Minor
>             Fix For: Future
>
>
> git.commit.id.abbrev=a84f7b9
> When querying for BOOT options, we get null for 'kind' for many of these 
> options:
> {code}
> +------------+------------+------------+------------+------------+------------+------------+
>  
> |    name    |    kind    |    type    |  num_val   | string_val |  bool_val  
> | float_val  | 
> +------------+------------+------------+------------+------------+------------+------------+
>  
> | drill.exec.buffer.impl | null       | BOOT       | null       | 
> "org.apache.drill.exec.work.batch.UnlimitedRawBatchBuffer" | null       | 
> null       |                                                            
> | drill.exec.buffer.size | null       | BOOT       | null       | "6"        
> | null       | null       |  
> | drill.exec.cluster-id | null       | BOOT       | null       | 
> "cluster105-drillbits" | null       | null       |
> {code}
> In contrast, for other options, we get meaningful values for 'kind':
> {code}
> 0: jdbc:drill:> select * from sys.options where type = 'BOOT' and kind is not 
> null order by name;         
> +------------+------------+------------+------------+------------+------------+------------+
>               
> |    name    |    kind    |    type    |  num_val   | string_val |  bool_val  
> | float_val  |              
> +------------+------------+------------+------------+------------+------------+------------+
>               
> | drill.client.supports-complex-types | BOOLEAN    | BOOT       | null       
> | null       | true       | null       |
> {code}
> It appears to make sense to have the right values for the 'kind' column.



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

Reply via email to