[ 
https://issues.apache.org/jira/browse/BEAM-1893?focusedWorklogId=220034&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-220034
 ]

ASF GitHub Bot logged work on BEAM-1893:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Mar/19 14:39
            Start Date: 28/Mar/19 14:39
    Worklog Time Spent: 10m 
      Work Description: aromanenko-dev commented on issue #8152: 
[DoNotMerge][BEAM-1893] Implementation of CouchbaseIO
URL: https://github.com/apache/beam/pull/8152#issuecomment-477623698
 
 
   @iemejia I'm not sure that `couch_total_disk_size` works in this case but 
It's possible to get a [bucket 
statistics](https://docs.couchbase.com/server/6.0/rest-api/rest-bucket-info.html)
 which provides `dataUsed` per bucket. So, we could potentially use this but 
there is another problem - there is no way (or I missed something?) to obtain 
mappings between bucket shards and offset/key ranges to create a proper splits. 
If there were such mapping then I believe we can use `BoundedSource` API.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 220034)
    Time Spent: 1h 40m  (was: 1.5h)

> Add IO module for Couchbase
> ---------------------------
>
>                 Key: BEAM-1893
>                 URL: https://issues.apache.org/jira/browse/BEAM-1893
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-ideas
>            Reporter: Xu Mingmin
>            Assignee: LI Guobao
>            Priority: Major
>              Labels: Couchbase, IO, features, triaged
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Create a {{CouchbaseIO}} for Couchbase database.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to