[jira] [Updated] (KAFKA-3526) REST APIs return object representation instead of string for config values, default values and recommended values

[Ismael Juma (JIRA)]

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

Ismael Juma updated KAFKA-3526:
---
Fix Version/s: (was: 0.10.1.0)

> REST APIs return object representation instead of string for config values, 
> default values and recommended values 
> --
>
> Key: KAFKA-3526
> URL: https://issues.apache.org/jira/browse/KAFKA-3526
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 0.10.0.0
>Reporter: Liquan Pei
>Assignee: Liquan Pei
> Fix For: 0.10.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In the response of 
> {code}
> PUT /connector-plugins/{name}/config/validate
> {code}
> The value.value, value.recommended_values and definition.default_value (If 
> the ConfigKey is not String type) are serialized by Jackson to something 
> other than strings.
> We actually expect the values to be strings, and this should mirror the 
> current requirements of submitting configs which is that the config is a 
> Map.
> This can be fixed by adding ConfigDef support for converting values to 
> strings, corresponding to all the parse methods, and then making sure all 
> these outputs of values have type String instead of Object.



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

[jira] [Updated] (KAFKA-3526) REST APIs return object representation instead of string for config values, default values and recommended values

[Gwen Shapira (JIRA)]

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

Gwen Shapira updated KAFKA-3526:

Fix Version/s: 0.10.0.0

> REST APIs return object representation instead of string for config values, 
> default values and recommended values 
> --
>
> Key: KAFKA-3526
> URL: https://issues.apache.org/jira/browse/KAFKA-3526
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 0.10.0.0
>Reporter: Liquan Pei
>Assignee: Liquan Pei
> Fix For: 0.10.1.0, 0.10.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In the response of 
> {code}
> PUT /connector-plugins/{name}/config/validate
> {code}
> The value.value, value.recommended_values and definition.default_value (If 
> the ConfigKey is not String type) are serialized by Jackson to something 
> other than strings.
> We actually expect the values to be strings, and this should mirror the 
> current requirements of submitting configs which is that the config is a 
> Map.
> This can be fixed by adding ConfigDef support for converting values to 
> strings, corresponding to all the parse methods, and then making sure all 
> these outputs of values have type String instead of Object.



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

[jira] [Updated] (KAFKA-3526) REST APIs return object representation instead of string for config values, default values and recommended values

[Ewen Cheslack-Postava (JIRA)]

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

Ewen Cheslack-Postava updated KAFKA-3526:
-
   Resolution: Fixed
Fix Version/s: (was: 0.11.0.0)
   0.10.1.0
   Status: Resolved  (was: Patch Available)

Issue resolved by pull request 1200
[https://github.com/apache/kafka/pull/1200]

> REST APIs return object representation instead of string for config values, 
> default values and recommended values 
> --
>
> Key: KAFKA-3526
> URL: https://issues.apache.org/jira/browse/KAFKA-3526
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 0.10.0.0
>Reporter: Liquan Pei
>Assignee: Liquan Pei
> Fix For: 0.10.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In the response of 
> {code}
> PUT /connector-plugins/{name}/config/validate
> {code}
> The value.value, value.recommended_values and definition.default_value (If 
> the ConfigKey is not String type) are serialized by Jackson to something 
> other than strings.
> We actually expect the values to be strings, and this should mirror the 
> current requirements of submitting configs which is that the config is a 
> Map.
> This can be fixed by adding ConfigDef support for converting values to 
> strings, corresponding to all the parse methods, and then making sure all 
> these outputs of values have type String instead of Object.



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

[jira] [Updated] (KAFKA-3526) REST APIs return object representation instead of string for config values, default values and recommended values

[Liquan Pei (JIRA)]

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

Liquan Pei updated KAFKA-3526:
--
Description: 
In the response of 
{code}
PUT /connector-plugins/{name}/config/validate
{code}
The value.value, value.recommended_values and definition.default_value (If the 
ConfigKey is not String type) are serialized by Jackson to something other than 
strings.

We actually expect the values to be strings, and this should mirror the current 
requirements of submitting configs which is that the config is a Map.

This can be fixed by adding ConfigDef support for converting values to strings, 
corresponding to all the parse methods, and then making sure all these outputs 
of values have type String instead of Object.

  was:
In the response of 
{code}
PUT /connector-plugins/{name}/config/validate
{code}
The value.value, value.recommended_values (which there are none in this 
example...), and definition.default_value (If the ConfigKey is not String type) 
are serialized by Jackson to something other than strings.

We actually expect the values to be strings, and this should mirror the current 
requirements of submitting configs which is that the config is a Map.

This can be fixed by adding ConfigDef support for converting values to strings, 
corresponding to all the parse methods, and then making sure all these outputs 
of values have type String instead of Object.


> REST APIs return object representation instead of string for config values, 
> default values and recommended values 
> --
>
> Key: KAFKA-3526
> URL: https://issues.apache.org/jira/browse/KAFKA-3526
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 0.10.0.0
>Reporter: Liquan Pei
>Assignee: Liquan Pei
> Fix For: 0.11.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In the response of 
> {code}
> PUT /connector-plugins/{name}/config/validate
> {code}
> The value.value, value.recommended_values and definition.default_value (If 
> the ConfigKey is not String type) are serialized by Jackson to something 
> other than strings.
> We actually expect the values to be strings, and this should mirror the 
> current requirements of submitting configs which is that the config is a 
> Map.
> This can be fixed by adding ConfigDef support for converting values to 
> strings, corresponding to all the parse methods, and then making sure all 
> these outputs of values have type String instead of Object.



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

[jira] [Updated] (KAFKA-3526) REST APIs return object representation instead of string for config values, default values and recommended values

[Liquan Pei (JIRA)]

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

Liquan Pei updated KAFKA-3526:
--
Description: 
In the response of 
PUT /connector-plugins/{name}/config/validate, 
The value.value, value.recommended_values (which there are none in this 
example...), and definition.default_value (If the ConfigKey is not String type) 
are serialized by Jackson to something other than strings.

We actually expect the values to be strings, and this should mirror the current 
requirements of submitting configs which is that the config is a Map.

This can be fixed by adding ConfigDef support for converting values to strings, 
corresponding to all the parse methods, and then making sure all these outputs 
of values have type String instead of Object.

  was:
In the response of 
{code}
PUT /connector-plugins/{name}/config/validate
{code}, 
The value.value, value.recommended_values (which there are none in this 
example...), and definition.default_value (If the ConfigKey is not String type) 
are serialized by Jackson to something other than strings.

We actually expect the values to be strings, and this should mirror the current 
requirements of submitting configs which is that the config is a Map.

This can be fixed by adding ConfigDef support for converting values to strings, 
corresponding to all the parse methods, and then making sure all these outputs 
of values have type String instead of Object.


> REST APIs return object representation instead of string for config values, 
> default values and recommended values 
> --
>
> Key: KAFKA-3526
> URL: https://issues.apache.org/jira/browse/KAFKA-3526
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 0.10.0.0
>Reporter: Liquan Pei
>Assignee: Liquan Pei
> Fix For: 0.11.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In the response of 
> PUT /connector-plugins/{name}/config/validate, 
> The value.value, value.recommended_values (which there are none in this 
> example...), and definition.default_value (If the ConfigKey is not String 
> type) are serialized by Jackson to something other than strings.
> We actually expect the values to be strings, and this should mirror the 
> current requirements of submitting configs which is that the config is a 
> Map.
> This can be fixed by adding ConfigDef support for converting values to 
> strings, corresponding to all the parse methods, and then making sure all 
> these outputs of values have type String instead of Object.



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