What are the concurrency guarantees for Flowable.merge()2019 Community Moderator ElectionHandling backpressure without dropping items or serializing in RxJavaHow do I conditionally buffer a Grouped Observable/Flux based on Emitted Events?Creating a Flowable that emits items at a limited rate to avoid the need to buffer eventsRx Java 2 Sync vs. AsyncRxJava2 - order of subscribing in chainUpdate and retain existing data with RxJavaCombining latest value with last n valuesRxJava map observable differently once another completable completesHow to filter values that change over delta thresholdRxJava - Use flowables async way
Best approach to update all entries in a list that is paginated?
Can you reject a postdoc offer after the PI has paid a large sum for flights/accommodation for your visit?
"However" used in a conditional clause?
Time dilation for a moving electronic clock
Who is our nearest neighbor
Am I not good enough for you?
Does anyone draw a parallel between Haman selling himself to Mordechai and Esav selling the birthright to Yaakov?
What does おとこえしや mean?
Co-worker team leader wants to inject the crap software product of his friends into our development. What should I say to our common boss?
Provisioning profile doesn't include the application-identifier and keychain-access-groups entitlements
What Happens when Passenger Refuses to Fly Boeing 737 Max?
US to Europe trip with Montreal layover - is 52 minutes enough?
Should we release the security issues we found in our product as CVE or we can just update those on weekly release notes?
Welcoming 2019 Pi day: How to draw the letter π?
What exactly is the purpose of connection links straped between the rocket and the launch pad
What is the blue range indicating on this manifold pressure gauge?
Latest web browser compatible with Windows 98
Need some help with my first LaTeX drawing…
Deleting missing values from a dataset
How to make readers know that my work has used a hidden constraint?
What happens with multiple copies of Humility and Glorious Anthem on the battlefield?
Running a subshell from the middle of the current command
Is it ok to include an epilogue dedicated to colleagues who passed away in the end of the manuscript?
What is the difference between "shut" and "close"?
What are the concurrency guarantees for Flowable.merge()
2019 Community Moderator ElectionHandling backpressure without dropping items or serializing in RxJavaHow do I conditionally buffer a Grouped Observable/Flux based on Emitted Events?Creating a Flowable that emits items at a limited rate to avoid the need to buffer eventsRx Java 2 Sync vs. AsyncRxJava2 - order of subscribing in chainUpdate and retain existing data with RxJavaCombining latest value with last n valuesRxJava map observable differently once another completable completesHow to filter values that change over delta thresholdRxJava - Use flowables async way
I've looked in details into the documentation of RxJava's Flowable.merge() operator, but I can't find the information I need.
My understanding, after some experimentation, is that given n upstream flowables Fi that are each emitting values in their own thread Ti, the merge operator guarantees that the merged flowable emits those values in a serialized fashion, such that the downstream has observed it before emitting the previous one. Experimentation also says that, by default a value Vi is observed by the downstream flowable in the same thread Ti as it was emitted.
This means that even if merge guarantees that the downstream receives values serially, it might observe them on different threads.
Now here's the question: Does RxJava guarantee that the observation of a value happens-before the observation of next value? Basically will all the changes made in memory while observing a value on Ti be visible while observing the next value on Tj?
rx-java2 reactivex
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
add a comment |
I've looked in details into the documentation of RxJava's Flowable.merge() operator, but I can't find the information I need.
My understanding, after some experimentation, is that given n upstream flowables Fi that are each emitting values in their own thread Ti, the merge operator guarantees that the merged flowable emits those values in a serialized fashion, such that the downstream has observed it before emitting the previous one. Experimentation also says that, by default a value Vi is observed by the downstream flowable in the same thread Ti as it was emitted.
This means that even if merge guarantees that the downstream receives values serially, it might observe them on different threads.
Now here's the question: Does RxJava guarantee that the observation of a value happens-before the observation of next value? Basically will all the changes made in memory while observing a value on Ti be visible while observing the next value on Tj?
rx-java2 reactivex
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
We have to, the spec mandates it: github.com/reactive-streams/reactive-streams-jvm#1.3
– akarnokd
Mar 7 at 11:32
Cool, that's what I was looking for. If you could turn that into an answer, I'll mark it as accepted.
– LordOfThePigs
Mar 7 at 14:43
Also, as a general comment: That page contains really important information that I wish was present in the Javadocs of the various interfaces. I would never have found that page (and therefore that information) without your link.
– LordOfThePigs
Mar 7 at 14:45
We are an open source project. If you think the documentation could benefit from expanding, please open a pull request.
– akarnokd
Mar 7 at 14:52
add a comment |
I've looked in details into the documentation of RxJava's Flowable.merge() operator, but I can't find the information I need.
My understanding, after some experimentation, is that given n upstream flowables Fi that are each emitting values in their own thread Ti, the merge operator guarantees that the merged flowable emits those values in a serialized fashion, such that the downstream has observed it before emitting the previous one. Experimentation also says that, by default a value Vi is observed by the downstream flowable in the same thread Ti as it was emitted.
This means that even if merge guarantees that the downstream receives values serially, it might observe them on different threads.
Now here's the question: Does RxJava guarantee that the observation of a value happens-before the observation of next value? Basically will all the changes made in memory while observing a value on Ti be visible while observing the next value on Tj?
rx-java2 reactivex
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
I've looked in details into the documentation of RxJava's Flowable.merge() operator, but I can't find the information I need.
My understanding, after some experimentation, is that given n upstream flowables Fi that are each emitting values in their own thread Ti, the merge operator guarantees that the merged flowable emits those values in a serialized fashion, such that the downstream has observed it before emitting the previous one. Experimentation also says that, by default a value Vi is observed by the downstream flowable in the same thread Ti as it was emitted.
This means that even if merge guarantees that the downstream receives values serially, it might observe them on different threads.
Now here's the question: Does RxJava guarantee that the observation of a value happens-before the observation of next value? Basically will all the changes made in memory while observing a value on Ti be visible while observing the next value on Tj?
rx-java2 reactivex
rx-java2 reactivex
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
asked Mar 7 at 10:55
LordOfThePigsLordOfThePigs
7,91133359
7,91133359
We have to, the spec mandates it: github.com/reactive-streams/reactive-streams-jvm#1.3
– akarnokd
Mar 7 at 11:32
Cool, that's what I was looking for. If you could turn that into an answer, I'll mark it as accepted.
– LordOfThePigs
Mar 7 at 14:43
Also, as a general comment: That page contains really important information that I wish was present in the Javadocs of the various interfaces. I would never have found that page (and therefore that information) without your link.
– LordOfThePigs
Mar 7 at 14:45
We are an open source project. If you think the documentation could benefit from expanding, please open a pull request.
– akarnokd
Mar 7 at 14:52
add a comment |
We have to, the spec mandates it: github.com/reactive-streams/reactive-streams-jvm#1.3
– akarnokd
Mar 7 at 11:32
Cool, that's what I was looking for. If you could turn that into an answer, I'll mark it as accepted.
– LordOfThePigs
Mar 7 at 14:43
Also, as a general comment: That page contains really important information that I wish was present in the Javadocs of the various interfaces. I would never have found that page (and therefore that information) without your link.
– LordOfThePigs
Mar 7 at 14:45
We are an open source project. If you think the documentation could benefit from expanding, please open a pull request.
– akarnokd
Mar 7 at 14:52
We have to, the spec mandates it: github.com/reactive-streams/reactive-streams-jvm#1.3
– akarnokd
Mar 7 at 11:32
We have to, the spec mandates it: github.com/reactive-streams/reactive-streams-jvm#1.3
– akarnokd
Mar 7 at 11:32
Cool, that's what I was looking for. If you could turn that into an answer, I'll mark it as accepted.
– LordOfThePigs
Mar 7 at 14:43
Cool, that's what I was looking for. If you could turn that into an answer, I'll mark it as accepted.
– LordOfThePigs
Mar 7 at 14:43
Also, as a general comment: That page contains really important information that I wish was present in the Javadocs of the various interfaces. I would never have found that page (and therefore that information) without your link.
– LordOfThePigs
Mar 7 at 14:45
Also, as a general comment: That page contains really important information that I wish was present in the Javadocs of the various interfaces. I would never have found that page (and therefore that information) without your link.
– LordOfThePigs
Mar 7 at 14:45
We are an open source project. If you think the documentation could benefit from expanding, please open a pull request.
– akarnokd
Mar 7 at 14:52
We are an open source project. If you think the documentation could benefit from expanding, please open a pull request.
– akarnokd
Mar 7 at 14:52
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55042118%2fwhat-are-the-concurrency-guarantees-for-flowable-merge%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55042118%2fwhat-are-the-concurrency-guarantees-for-flowable-merge%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
We have to, the spec mandates it: github.com/reactive-streams/reactive-streams-jvm#1.3
– akarnokd
Mar 7 at 11:32
Cool, that's what I was looking for. If you could turn that into an answer, I'll mark it as accepted.
– LordOfThePigs
Mar 7 at 14:43
Also, as a general comment: That page contains really important information that I wish was present in the Javadocs of the various interfaces. I would never have found that page (and therefore that information) without your link.
– LordOfThePigs
Mar 7 at 14:45
We are an open source project. If you think the documentation could benefit from expanding, please open a pull request.
– akarnokd
Mar 7 at 14:52