Skip to content

Releases: jcustenborder/kafka-connect-json-schema

0.2.5

19 May 19:28
c3f8b0e
Compare
Choose a tag to compare

Changelog

Unreleased

GitHub #10 Schemas that do not have titles can cause multiple schemas with no name to be defined. This breaks AVRO. bug

Extended the wikimedia test case to cover the entire schema. Added support to build a schema name for objects based on the location of the property. Fixes #10. (#11)

c3f8b0e968af55b Jeremy Custenborder 2020-05-19 19:25:23

GitHub #11 Extended the wikimedia test case to cover the entire schema. Added support to build a schema name for objects based on the location of the property. Fixes #10.

Extended the wikimedia test case to cover the entire schema. Added support to build a schema name for objects based on the location of the property. Fixes #10. (#11)

c3f8b0e968af55b Jeremy Custenborder 2020-05-19 19:25:23

0.2.4

18 May 20:20
7960bbc
Compare
Choose a tag to compare

Changelog

Unreleased

GitHub #8 java.lang.UnsupportedOperationException: Schema type is not supported.

Added support to exclude properties. Added fall through case for Strings to just be passed as a string. Fixes #8. (#9)

7960bbca6e1be7d Jeremy Custenborder 2020-05-18 20:17:31

GitHub #9 Added support to exclude properties. Added fall through case for Strings to just be passed as a string. Fixes #8.

Added support to exclude properties. Added fall through case for Strings to just be passed as a string. Fixes #8. (#9)

7960bbca6e1be7d Jeremy Custenborder 2020-05-18 20:17:31

0.2.3

02 Apr 03:56
239c64f
Compare
Choose a tag to compare

Changelog

Unreleased

GitHub #1 Initial

Initial (#1)

  • Initial commit. Conversion from a Json Schema to a Connect schema is working properly.
  • Mostly working except for arrays.
  • Round trip for a converter is working
  • Added license headers. Checkstyle.
  • Corrected to run on primitives
  • Added FromJson transformation.
  • Refactor towards having support for inline and file based configs.
  • Refactor towards having support for inline and file based configs.
  • Round trip decimal support.
  • Added example for FromJson.
  • Added support to inject a header when messages do not have a schema header.
  • Publish to the connect hub.

16cf9b346caa251 Jeremy Custenborder 2020-03-06 01:26:22

GitHub #2 Documentation should point out that transformation should use ByteArrayConverter or StringConverter enhancement

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #3 Add support to validate JSON enhancement

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #4 Add support for custom date formats enhancement

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #5 v 0.2

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #6 Confluent hub description is the default from the pom. bug

Corrected description in pom. Fixes #6. (#7)

239c64fa6404396 Jeremy Custenborder 2020-04-02 03:53:52

GitHub #7 Corrected description in pom. Fixes #6.

Corrected description in pom. Fixes #6. (#7)

239c64fa6404396 Jeremy Custenborder 2020-04-02 03:53:52

0.2.2: v 0.2 (#5)

02 Apr 00:56
c8626c8
Compare
Choose a tag to compare

Changelog

Unreleased

GitHub #1 Initial

Initial (#1)

  • Initial commit. Conversion from a Json Schema to a Connect schema is working properly.
  • Mostly working except for arrays.
  • Round trip for a converter is working
  • Added license headers. Checkstyle.
  • Corrected to run on primitives
  • Added FromJson transformation.
  • Refactor towards having support for inline and file based configs.
  • Refactor towards having support for inline and file based configs.
  • Round trip decimal support.
  • Added example for FromJson.
  • Added support to inject a header when messages do not have a schema header.
  • Publish to the connect hub.

16cf9b346caa251 Jeremy Custenborder 2020-03-06 01:26:22

GitHub #2 Documentation should point out that transformation should use ByteArrayConverter or StringConverter enhancement

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #3 Add support to validate JSON enhancement

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #4 Add support for custom date formats enhancement

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

GitHub #5 v 0.2

v 0.2 (#5)

  • Added documentation suggesting the use of the ByteArrayConverter or StringConverter. Added configuration setting to enable validation of the json messages. Violations will result in an exception being thrown. Fixes #2. Fixes #3
  • Added support for custom date formats. This allows the user to specify the date format for parsing. Fixes #4.

c8626c8176181de Jeremy Custenborder 2020-04-02 00:54:10

0.0.2.1: Initial (#1)

06 Mar 01:28
16cf9b3
Compare
Choose a tag to compare

Changelog

Unreleased

GitHub #1 Initial

Initial (#1)

  • Initial commit. Conversion from a Json Schema to a Connect schema is working properly.
  • Mostly working except for arrays.
  • Round trip for a converter is working
  • Added license headers. Checkstyle.
  • Corrected to run on primitives
  • Added FromJson transformation.
  • Refactor towards having support for inline and file based configs.
  • Refactor towards having support for inline and file based configs.
  • Round trip decimal support.
  • Added example for FromJson.
  • Added support to inject a header when messages do not have a schema header.
  • Publish to the connect hub.

16cf9b346caa251 Jeremy Custenborder 2020-03-06 01:26:22