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

[BUG] Potential eclipselink schema upgrade issue #450

Open
1 task done
snazy opened this issue Nov 15, 2024 · 0 comments
Open
1 task done

[BUG] Potential eclipselink schema upgrade issue #450

snazy opened this issue Nov 15, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@snazy
Copy link
Member

snazy commented Nov 15, 2024

Is this a possible security vulnerability?

  • This is NOT a possible security vulnerability

Describe the bug

The change #438 changes the database schema. However, there seems to be an issue that the schema is not properly updated - at least not via PolarisEclipseLinkMetaStoreManagerTest, see repro steps below.

/cc @eric-maynard

To Reproduce

  1. git checkout e232b000760da335721e9112f9d52fe041289613 (commit before Do not persist plaintext secrets in the metastore #438)
  2. rm -rf extension/persistence/eclipselink/build (just get a clean state)
  3. ./gradlew :polaris-eclipselink:test --rerun (passes fine)
  4. git checkout ab095cfab84e5b4e694c72011f4166589eb25f38 (Do not persist plaintext secrets in the metastore #438)
  5. ./gradlew :polaris-eclipselink:test --rerun (fails)
  6. rm -rf extension/persistence/eclipselink/build/test_data (database state)
  7. ./gradlew :polaris-eclipselink:test --rerun (passes fine)

Actual Behavior

No response

Expected Behavior

No response

Additional context

No response

System information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant