[ 
https://issues.apache.org/jira/browse/BAHIR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092462#comment-16092462
 ] 

ASF GitHub Bot commented on BAHIR-110:
--------------------------------------

Github user ckadner commented on the issue:

    https://github.com/apache/bahir/pull/45
  
    @emlaver -- the most recent build 
([77](http://169.45.79.58:8080/job/bahir_spark_pr_builder/77/)) ran with 
user/pwd env vars set ...
    
    ```
    Discovery completed in 185 milliseconds.
    Run starting. Expected test count is: 21
    CloudantOptionSuite:
    - invalid api receiver option throws an error message
    - empty username option throws an error message
    - empty password option throws an error message
    - empty databaseName throws an error message
    ClientSparkFunSuite:
    CloudantChangesDFSuite:
    - load and save data from Cloudant database
    - load and count data from Cloudant search index
    - load data and count rows in filtered dataframe
    - save filtered dataframe to database
    - save dataframe to database using createDBOnSave=true option
    - load and count data from view
    - load data from view with MapReduce function
    - load data and verify total count of selector, filter, and view option
    CloudantSparkSQLSuite:
    - verify results from temp view of database n_airportcodemapping
    - verify results from temp view of index in n_flight
    CloudantAllDocsDFSuite:
    - load and save data from Cloudant database
    - load and count data from Cloudant search index
    - load data and count rows in filtered dataframe
    - save filtered dataframe to database
    - save dataframe to database using createDBOnSave=true option
    - load and count data from view
    - load data from view with MapReduce function
    
    Run completed in 2 minutes, 58 seconds.
    Total number of tests run: 21
    Suites: completed 6, aborted 0
    Tests: succeeded 21, failed 0, canceled 0, ignored 0, pending 0
    
    All tests passed.
    ```


> 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
>   Original Estimate: 216h
>  Remaining Estimate: 216h
>
> 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.4.14#64029)

Reply via email to