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

UpdateBinary algorithm #421

Closed
kavics opened this Issue Jul 23, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@kavics
Copy link
Contributor

kavics commented Jul 23, 2018

Symptom:

The update binary property algorithm is not acceptable because it can copy between two streams in more roundtrip based on one File row.

Expectations

  • Copy source can be untouched but:
  • The target has to be a new File row with the following properties:
    • Target provider name.
    • Target provider data.
    • Active staging flag to avoid deletion.
  • At the end of the operation:
    • The staging flag needs to be deleted
    • The current BinaryProperty row needs to point to the new File row.

The bug probably affects all metadata providers so after/during the fix, integration tests must be prepared for:

  • MsSqlBlobMetaDataProvider (built-in)
  • SqlFileStreamBlobMetaDataProvider (legacy)
  • InMemoryBlobStorageMetaDataProvider (tests)

@kavics kavics added this to the Sprint 163 milestone Jul 23, 2018

@kavics kavics self-assigned this Jul 23, 2018

@kavics kavics added the bug label Jul 23, 2018

@kultsar kultsar closed this Jul 25, 2018

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