You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bahir.apache.org by "Esteban Laver (JIRA)" <ji...@apache.org> on 2017/04/24 15:01:04 UTC

[jira] [Created] (BAHIR-110) Replace use of _all_docs API with _changes API in all receivers

Esteban Laver created BAHIR-110:
-----------------------------------

             Summary: Replace use of _all_docs API with _changes API in all receivers
                 Key: BAHIR-110
                 URL: https://issues.apache.org/jira/browse/BAHIR-110
             Project: Bahir
          Issue Type: Improvement
            Reporter: Esteban Laver


Today we use the _changes API for Spark streaming receiver and _all_docs API for non-streaming receiver. _all_docs API supports parallel reads (using offset and range) but performance of _changes API is still better in most cases (even with single threaded support).

With this ticket we want to:
a) re-implement all receivers using _changes API
b) compare performance between the two implementations based on _changes and _all_docs

Based on the results in b) we could decide to either
- replace _all_docs implementation with _changes based implementation OR
- allow customers to pick one (with a solid documentation about pros and cons) 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)