-
Notifications
You must be signed in to change notification settings - Fork 7
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
Ion to Json task fails when Ion file contains type annotation #138
Comments
Up to implementation, but we could also add a flag to let the user choose the behavior intented (ie. remove annotation metadata from JSON or add a field |
Being able to do both would indeed be awesome. |
It seems to be a bug with the IonMapper, I'll try to create a reproducer to open a bug upstream. |
@ReLoutre can you add in a comment the way to generate this base64 annotated field? |
In my case I'm using the Java |
PS: Take note that |
In my opinion, the problem is highly related to the following issue. |
Describe the issue
Using IonToJson task on a file that contains a type annotated value produce infinite nested call of IonSystemLite['loader"] and IonStringLite["system"].
Bug reproduction
Here's a flow to reproduce the error :
Here's the content of the file to input in the flow :
Removing the type annotation
base64::
works fine.Expecting behaviour :
While downgrading to JSON type annotation may be totally erased or concerned field may be translated as :
For example...
Environment
Error encountered
The text was updated successfully, but these errors were encountered: