[jira] [Commented] (BEAM-11155) Series.str.repeat zipping operation produces incorrect proxy

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-11155:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Series.str.repeat zipping operation produces incorrect proxy
> ------------------------------------------------------------
>
>                 Key: BEAM-11155
>                 URL: https://issues.apache.org/jira/browse/BEAM-11155
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Brian Hulette
>            Priority: P2
>              Labels: stale-P2
>
> https://github.com/apache/beam/pull/13139#discussion_r513684704
> This proxy is incorrectly inferred as bool.
> {code}
> In [10]: proxy.dtypes
> Out[10]: 
> str        object
> repeats     int64
> dtype: object
> In [11]: proxy.str.str.repeat(proxy.repeats)
> Out[11]: Series([], Name: str, dtype: bool)
> {code}
> The actual operation does produce object though:
> {code}
> In [13]: df.str.str.repeat(df.repeats)
> Out[13]: 
> 0      AAA
> 1        B
> 2     CCCC
> 3    DDDDD
> 4       EE
> Name: str, dtype: object
> {code}
> Currently we work around this by specifying the proxy manually, maybe it can be fixed upstream?



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