Spike#2
Conversation
added option to normalise groups and components
* change to mvn co-ordinates so a release of this project can be made before io.fixprotocol original version is released
* change to mvn co-ordinates so a release of this prject can be made before io.fixprotocol original branch is released
* change to mvn co-ordinates so a release of this project can be made before io.fixprotocol original branch is released
* added distribution management
* change to mvn co-ordinates so a release of this prject can be made before io.fixprotocol original branch is released
* change to mvn co-ordinates so a release of this prject can be made before io.fixprotocol original branch is released
* change to mvn co-ordinates so a release of this prject can be made before io.fixprotocol original branch is released
donmendelson
left a comment
There was a problem hiding this comment.
The FIX field types are mapped directly to Avro primitive types, many mapped to string. I'm concerned that some specialization is lost. For example, how is a timestamp written as a string in such a way that can be interpreted correctly by a reader. I see that Avro has "logical types", such as date and timestamp. Shouldn't we use those? For flexibility, mapping could be written in an Orchestra file as element mappedDatatype rather than hardcoding. The code doesn't consult the datatypes section at all.
I have added the datatype mappings and also support for Avro Logical Types. |
This is a PR for tools to generate Apache Avro schemas from a FIX Orchestra repository. I think the best way to review this is to check it out and build it, there are READMEs in the project. If this is worthy; and following review, should the PR be approved, and before merging to main, please create the following Action Secrets for the organisation. This will permit the release to the Sonatype OSS Repository Hosting repository to be made by GitHub Actions workflows in the project. Also please make the Action Secrets available to this repository in the settings. These secrets are encrypted and cannot be viewed by collaborators. The secrets that this plan expects are :
If these secrets already exist in the Action Secrets I can of course update the .github/workflows/release-and-publish.yml.
Ref : https://central.sonatype.org/publish/publish-maven/#performing-a-release-deployment-with-the-maven-release-plugin