Skip to content

FMWK-467 Issue using refs with yaml file#159

Closed
tim-aero wants to merge 2 commits intomainfrom
issue-using-refs-with-yaml-file
Closed

FMWK-467 Issue using refs with yaml file#159
tim-aero wants to merge 2 commits intomainfrom
issue-using-refs-with-yaml-file

Conversation

@tim-aero
Copy link
Contributor

Fixed a null pointer exception when using refs via the YAML file, caused by BatchLoad being null and reading code incorrectly assuming a valid value.

tim-aero added 2 commits May 19, 2024 20:37
If a policy specified either by defaultPolicy or using the policy
hierarchy has a RecordExistsAction of CREATE_ONLY, the save method was
overwriting this with REPLACE. Changed this to only replace the policy
with REPLACE if the passed RecordExistsAction is UPDATE.
Whilst references work correctly with annotations, they would throw a
NullPointerException when being used with an external configuration such
as a YAML file. The issue was caused by the `BatchLoad` property which
was initialized by default to true on the annotation but was left as
null if not specified in the file
@tim-aero tim-aero requested a review from roimenashe June 14, 2024 16:39
@roimenashe
Copy link
Member

@tim-aero I have no problem with the refs with yaml file changes but this PR contains changes of #158 which we might not push to main at this point (we still haven't reviewed the refactor alternatives, didn't have the capacity and the user has a workaround for now).

issue-using-refs-with-yaml-file branch should've been created from main instead of issue-with-insert-only-policy to contain specific changes to solve this issue.

@roimenashe roimenashe changed the title Issue using refs with yaml file FMWK-467 Issue using refs with yaml file Jun 18, 2024
@roimenashe
Copy link
Member

See #161

@roimenashe roimenashe closed this Jun 18, 2024
@reugn reugn deleted the issue-using-refs-with-yaml-file branch July 31, 2024 14:18
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