Skip to content

Conversation

@kiersten-stokes
Copy link
Member

Fixes #3010

What changes were proposed in this pull request?

DisableNodeCaching currently requires special handling, as it is our only Elyra-owned property that is not stored and processed as an object. As a result, values weren't being stored in their instances properly and therefore weren't propagating properly. This PR adds a should_discard method to DisableNodeCaching in order to: 1.) fix the propagation issue now, and 2.) prepare for when this property is finally converted into an object-valued property in the pipeline JSON.

How was this pull request tested?

I added a case to an existing test because this has unfortunately come up before. We could potentially remove this case if desired once we switch the handling/storage of DisableNodeCaching to an object-valued properly. Instead, however, we should probably have a test case for each Elyra-owned property.

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@kiersten-stokes kiersten-stokes added kind:bug Something isn't working impact:blocker labels Nov 14, 2022
@kiersten-stokes kiersten-stokes added this to the 3.13.0 milestone Nov 14, 2022
@elyra-bot
Copy link

elyra-bot bot commented Nov 14, 2022

Thanks for making a pull request to Elyra!

To try out this branch on binder, follow this link: Binder

Copy link
Member

@kevin-bates kevin-bates left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. My only comment is regarding the dual types that need to be handled (which is kind of a hassle) and just wondering if this is historical (and avoids a migration).

Copy link
Member

@ptitzler ptitzler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@akchinSTC akchinSTC merged commit 1440e25 into elyra-ai:main Nov 14, 2022
Copy link
Member

@kevin-bates kevin-bates left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

impact:blocker kind:bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pipeline defaults are not properly propagated

4 participants