Skip to content

DATAREDIS-711 - Emit Lua array responses as List. #282

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

Closed
wants to merge 6 commits into from

Conversation

mp911de
Copy link
Member

@mp911de mp911de commented Oct 5, 2017

We now emit array responses from Lua script execution as complete List instead of emitting the individual elements through the Publisher.

Lua scripts may return nil (null) elements that would be not emitted through a Publisher. Skipping null values would garble up the response – and in several cases, the response array is required as List. Emitting the whole List aligns the response to the signatures imposed by generics and aligns the behavior with the imperative API.

Fix value serialization by using the configured value serializer when serializing Lua script arguments.


Related ticket: DATAREDIS-711.

We now emit array responses from Lua script execution as complete List instead of emitting the individual elements through the Publisher.

Lua scripts may return nil (null) elements that would be not emitted through a Publisher. Skipping null values would garble up the response – and in several cases, the response array is required as List. Emitting the whole List aligns the response to the signatures imposed by generics and aligns the behavior with the imperative API.
Use the configured value serializer for Lua argument serialization.
Strenghen non-null requirements when obtaining the native connection from LettuceReactiveRedisConnection. Guard close against multiple calls.
christophstrobl pushed a commit that referenced this pull request Oct 11, 2017
We now emit array responses from Lua script execution as complete List instead of emitting the individual elements through the Publisher.

Lua scripts may return nil (null) elements that would be not emitted through a Publisher. Skipping null values would garble up the response – and in several cases, the response array is required as List. Emitting the whole List aligns the response to the signatures imposed by generics and aligns the behavior with the imperative API.

Original Pull Request: #282
christophstrobl pushed a commit that referenced this pull request Oct 11, 2017
Strengthen non-null requirements when obtaining the native connection from LettuceReactiveRedisConnection. Guard close against multiple calls and use concatMap instead of flatMap to retain publisher sequence.

Original Pull Request: #282
christophstrobl added a commit that referenced this pull request Oct 11, 2017
Retain publisher sequence by using concatMap, remove trailing whitespace, flush script cache in tests.

Original Pull Request: #282
@christophstrobl christophstrobl deleted the issue/DATAREDIS-711 branch October 11, 2017 09:36
christophstrobl pushed a commit that referenced this pull request Oct 12, 2017
We now emit array responses from Lua script execution as complete List instead of emitting the individual elements through the Publisher.

Lua scripts may return nil (null) elements that would be not emitted through a Publisher. Skipping null values would garble up the response – and in several cases, the response array is required as List. Emitting the whole List aligns the response to the signatures imposed by generics and aligns the behavior with the imperative API.

Original Pull Request: #282
christophstrobl pushed a commit that referenced this pull request Oct 12, 2017
Strengthen non-null requirements when obtaining the native connection from LettuceReactiveRedisConnection. Guard close against multiple calls and use concatMap instead of flatMap to retain publisher sequence.

Original Pull Request: #282
christophstrobl added a commit that referenced this pull request Oct 12, 2017
Retain publisher sequence by using concatMap, remove trailing whitespace, flush script cache in tests.

Original Pull Request: #282
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants