Skip to content

Encoded cursor response.

Hema Vishnu Pola [Microsoft] requested to merge fixing-cursor-query into master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)
#48 (closed)

Does this introduce a change in the core logic?

  • [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

The cursor is not being encoded, which is causing problems when making continuation queries.

What is the new/expected behavior?

The cursor value is encoded so the next time continuation queries need not worry about any encoding issues.

Have you added/updated Unit Tests and Integration Tests?

Yes, added unit test which otherwise did not cover for test coverage of the cursor flow of code.

Any other useful information

Have initially started to use URLEncoding mechanism, but then discovered in the tests that Spring framework is already doing the decoding when the query param reaches to the handler. Again doing URLDecoding in the handler was causing data loss (it was removing + characters as it was assuming them to be encoded characters), so moved to basae64 encoding and decoding.

Edited by Hema Vishnu Pola [Microsoft]

Merge request reports