spring-projects / spring-projects/spring-data-rest

Update test cases/documentation when Spring Data Cassandra is updated to handle nulls [DATAREST-456]

Open
#835 1 comment 0 reactions 1 assignee View on GitHub

@gregturn is already working on this.

Since Dec 31, 2020.

in: repository type: documentation type: enhancement
Dominant language
Java
Stars
958
Forks
568
PR merge metrics
No merged PRs in 30d

Description

Greg Turnquist opened DATAREST-456 and commented

There is an automated test case that shows Spring Data Cassandra's behavior regarding an upsert. This should break when Spring Data Cassandra itself is fixed. This issue is meant to track fixing that with proper behavior.

If any documentation is also written, clean that up as well


Issue Links:

  • DATACASS-194 Add ability to update/store null into fields
    ("depends on")
  • DATACASS-182 Ability to null out column values
    ("depends on")

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.