Skip to content
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

Remove extra code when spark-xml handles empty arrays #417

Closed
benedeki opened this issue May 27, 2019 · 1 comment · Fixed by #1783
Closed

Remove extra code when spark-xml handles empty arrays #417

benedeki opened this issue May 27, 2019 · 1 comment · Fixed by #1783
Assignees
Labels
3rd party issue Issue not our own in origin but we are slowed down by them priority: low Nice to have question Further information is requested refactoring Improving code quality, paying off tech debt, aligning API, cleanup of unused code Standardization Standardization Job affected

Comments

@benedeki
Copy link
Collaborator

Remove extra code in StandardizationInterpreter when spark-xml handles empty arrays

@benedeki benedeki added Standardization Standardization Job affected workaround labels May 27, 2019
@Zejnilovic Zejnilovic added question Further information is requested under discussion Requires consideration before a decision is made whether/how to implement labels May 28, 2019
@Zejnilovic
Copy link
Contributor

We need to find if this is an actually a bug or a feature of theirs.

@GeorgiChochov GeorgiChochov added 3rd party issue Issue not our own in origin but we are slowed down by them refactoring Improving code quality, paying off tech debt, aligning API, cleanup of unused code question Further information is requested priority: low Nice to have and removed question Further information is requested under discussion Requires consideration before a decision is made whether/how to implement labels Oct 7, 2019
dk1844 added a commit that referenced this issue May 12, 2021
@dk1844 dk1844 linked a pull request May 12, 2021 that will close this issue
dk1844 added a commit that referenced this issue May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rd party issue Issue not our own in origin but we are slowed down by them priority: low Nice to have question Further information is requested refactoring Improving code quality, paying off tech debt, aligning API, cleanup of unused code Standardization Standardization Job affected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants