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

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

                Author: ASF GitHub Bot
            Created on: 03/Nov/21 19:23
            Start Date: 03/Nov/21 19:23
    Worklog Time Spent: 10m 
      Work Description: tvalentyn commented on pull request #15775:
URL: https://github.com/apache/beam/pull/15775#issuecomment-959849272


   git can be tricky to deal with sometimes. But you can usually revert to a 
happy state by looking up revisions, and resetting to a known healthy state, 
like:
   
   ```
   git reflog --oneline
   git reset --hard  HEAD@{7}
   ```
   
   then, you could rebase changes on top of other branches, via smth like:
   
   ```
   git pull --rebase=interactive origin master 
   ```
   or in your case, origin might have been a master from your fork, so you'd 
probably do smth like
   
   ```
   git pull --rebase=interactive apache master 
   ```
   
   You can assuming `apache` tracks the main repo. You can also do pull and 
rebase in separate commands. But yes, I find the workflow easier if origin is 
already tracks the apache repo.
   
   You can also force-push any local branch to the branches you control, so 
that you don't have to create separate PRs from another branch (but that works 
too of course).


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 674874)
    Time Spent: 24h 50m  (was: 24h 40m)

> Add custom delimiters to Python TextIO reads
> --------------------------------------------
>
>                 Key: BEAM-12730
>                 URL: https://issues.apache.org/jira/browse/BEAM-12730
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-py-common, io-py-files
>            Reporter: Daniel Oliveira
>            Assignee: Dmitrii Kuzin
>            Priority: P2
>              Labels: beginner, newbie, starter
>             Fix For: 2.34.0
>
>          Time Spent: 24h 50m
>  Remaining Estimate: 0h
>
> A common request by users is to be able to separate a text files read by 
> TextIO with delimiters other than newline. The Java SDK already supports this 
> feature.
> The current delimiter code is [located 
> here|https://github.com/apache/beam/blob/v2.31.0/sdks/python/apache_beam/io/textio.py#L236]
>  and defaults to newlines. This function could easily be modified to also 
> handle custom delimiters. Changing this would also necessitate changing the 
> API for the various TextIO.Read methods and adding documentation.
> This seems like a good starter bug for making more in-depth contributions to 
> Beam Python.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to