[
https://issues.apache.org/jira/browse/STORM-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-2187:
--------------------------------
Description:
We're now serializing record into a ByteBuffer and store it to a single field.
That was needed for Kafka and Redis, but I feel it's not natural for some data
sources which supports schema (like JDBC, MongoDB, etc.)
For these data sources, record should be stored as it is (not serialized).
If new approach doesn't break backward compatibility it should be great, but if
it's necessary to break, I think it's OK to break since Storm SQL is still
marked as 'experiment'.
was:
We're now serializing record into a ByteBuffer and store it to a single field.
That was needed to Kafka and Redis, but I feel it's not natural for some data
sources which supports schema (like JDBC, MongoDB, etc.)
For these data sources, record should be stored as it is (not serialized).
If new approach doesn't break backward compatibility it should be great, but if
it's necessary to break, I think it's OK to break since Storm SQL is still
marked as 'experiment'.
> [Storm SQL] Finding a way to store the values in record to matching fields
> --------------------------------------------------------------------------
>
> Key: STORM-2187
> URL: https://issues.apache.org/jira/browse/STORM-2187
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-sql
> Reporter: Jungtaek Lim
>
> We're now serializing record into a ByteBuffer and store it to a single field.
> That was needed for Kafka and Redis, but I feel it's not natural for some
> data sources which supports schema (like JDBC, MongoDB, etc.)
> For these data sources, record should be stored as it is (not serialized).
> If new approach doesn't break backward compatibility it should be great, but
> if it's necessary to break, I think it's OK to break since Storm SQL is still
> marked as 'experiment'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
