[
https://issues.apache.org/jira/browse/BAHIR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082924#comment-16082924
]
ASF GitHub Bot commented on BAHIR-110:
--------------------------------------
Github user emlaver commented on a diff in the pull request:
https://github.com/apache/bahir/pull/45#discussion_r126801090
--- Diff: sql-cloudant/README.md ---
@@ -31,15 +31,14 @@ The `--packages` argument can also be used with
`bin/spark-submit`.
Submit a job in Python:
- spark-submit --master local[4] --jars <path to cloudant-spark.jar>
<path to python script>
+ spark-submit --master local[4] --packages
org.apache.bahir:spark-sql-cloudant_2.11:2.2.0-SNAPSHOT <path to python
script>
--- End diff --
Fixed in 5588c87. There are existing examples on how to run this command
under sections `Using SQL In Python` and `Using SQL In Scala`.
> 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)
