8000 TargetRetriever addition and Optional data with SchemaDetails by koushikr · Pull Request #18 · grookage/leia · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

TargetRetriever addition and Optional data with SchemaDetails #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
Jan 27, 2025

Conversation

koushikr
Copy link
Member
@koushikr koushikr commented Jan 22, 2025
  • LeiaMessageProduceClient
    • Introduced a TargetValidator for dynamically validating transformation targets.
    • Both the messageProcessor and the target validator can be runtime args along with initialzied values
    • No exception on a schema not present in the client side
  • SchemaDetails :
    • Introduced JsonNode along with SchemaDetails, clients can keep custom data with their schema
      definitions if required
    • Supporting the latest version match. In the SchemaDefinition latest version could be provided instead of the
      exact version.
  • TransformationTarget :
    • Introduced a criteria to validate transformation targets based on source object
  • Multiple Version Support:
    • Support to handle multiple schema versions. Introduced histories at a SchemaDetails level to incubate the
      necessary
      information.
  • SchemaAttribute:
    • Introduced a DateAttribute for explicitly validating Date
  • Aerospike Repository:
    • Support for AS data store, along with the dw bundle

Also introduced the processor module and a place holder for http-processor, for adding more message processors

    - Introduced a targetRetriever for dynamically computing transformation targets.
    - Both the messageProcessor and the target retriever can be runtime args along with initialzied values
- SchemaDetails : Introduced JsonNode along with SchemaDetails, clients can keep custom data with their schema definitions if required
@subham-soni
Copy link
Contributor
subham-soni commented Jan 24, 2025

With multiple versions supported, client code will have pojo for only one version of a schema and this exception doesn't make sense. Removed it in the other branch here

Rest LGTM

@koushikr koushikr merged commit 9fb677c into master Jan 27, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0