[
https://issues.apache.org/jira/browse/KAFKA-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Fiore Vitale updated KAFKA-18299:
---------------------------------------
Description:
The current implementation restricts the usage of data classes, which prevents
broader adoption and integration. By moving these classes to a separate module,
we can achieve:
* *More flexible for developers*
*
** Developers can now use these data classes outside of Kafka Connect
** It makes it easier to create consistent data models across different
applications
* *Cleaner project structure*
*
** Allows independent versioning of data format components
** Creates a clearer separation of different parts of the Kafka ecosystem
* *Become standard for other Tools and Frameworks*
*
** It makes it easier for third-party tools to work with Kafka's data models
** Supports a more generic data format
** Helps different streaming platforms work together more smoothly
was:
The current implementation restricts the usage of data classes, which prevents
broader adoption and integration. By moving these classes to a separate module,
we can achieve:
* *More Flexible for Developers*
*
** Developers can now use these data classes outside of Kafka Connect
** It makes it easier to create consistent data models across different
applications
* *Cleaner Project Structure*
*
** Allows independent versioning of data format components
** Creates a clearer separation of different parts of the Kafka ecosystem
* *Become standard for other Tools and Frameworks*
*
** It makes it easier for third-party tools to work with Kafka's data models
** Supports a more generic data format
** Helps different streaming platforms work together more smoothly
> Promote Kafka Connect data package as a dedicated module
> --------------------------------------------------------
>
> Key: KAFKA-18299
> URL: https://issues.apache.org/jira/browse/KAFKA-18299
> Project: Kafka
> Issue Type: Wish
> Components: connect
> Reporter: Mario Fiore Vitale
> Assignee: Mario Fiore Vitale
> Priority: Major
>
> The current implementation restricts the usage of data classes, which
> prevents broader adoption and integration. By moving these classes to a
> separate module, we can achieve:
> * *More flexible for developers*
> *
> ** Developers can now use these data classes outside of Kafka Connect
> ** It makes it easier to create consistent data models across different
> applications
> * *Cleaner project structure*
> *
> ** Allows independent versioning of data format components
> ** Creates a clearer separation of different parts of the Kafka ecosystem
> * *Become standard for other Tools and Frameworks*
> *
> ** It makes it easier for third-party tools to work with Kafka's data models
> ** Supports a more generic data format
> ** Helps different streaming platforms work together more smoothly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
