ASF GitHub Bot commented on BEAM-639:

GitHub user dhalperi opened a pull request:


    [BEAM-639] BigtableIO: add support for users to scan table subranges

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dhalperi/incubator-beam bigtable-key-setters

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #969
commit 9796ae1ec09cd299cacd71ff80232bcf58f45cbd
Author: Dan Halperin <dhalp...@google.com>
Date:   2016-09-19T18:54:07Z

    [BEAM-639] BigtableIO: add support for users to scan table subranges


> BigtableIO.Read: expose withStartKey/withEndKey
> -----------------------------------------------
>                 Key: BEAM-639
>                 URL: https://issues.apache.org/jira/browse/BEAM-639
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-gcp
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>            Priority: Minor
> BigtableIO.Read takes a table and a filter, but does not let the user 
> customize the row range. If a user wants to scan a relatively narrow range, 
> they can do it by specifying a filter ("starts with abcd") or ("less than 
> abcd"), but under the hood Cloud Bigtable will implement this as a full table 
> scan -> filter instead of a narrower scan.
> We should expose these setters publicly so that users can implement row scans 
> directly.

This message was sent by Atlassian JIRA

Reply via email to