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

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

                Author: ASF GitHub Bot
            Created on: 04/Nov/21 01:28
            Start Date: 04/Nov/21 01:28
    Worklog Time Spent: 10m 
      Work Description: adude3141 commented on pull request #15856:
URL: https://github.com/apache/beam/pull/15856#issuecomment-959864900


   > It would be great to add a regression test for that
   
   Sure. Was looking into this, but could not find any tests regarding 
configuration or similar and could not come up with a simple but meaningful 
test case. If you could give some pointers to some comparable tests I d be 
willing to add some here too
   
   


-- 
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: 675790)
    Time Spent: 2h 20m  (was: 2h 10m)

> ParquetIO.parseGenericRecords does not support Configuration
> ------------------------------------------------------------
>
>                 Key: BEAM-13157
>                 URL: https://issues.apache.org/jira/browse/BEAM-13157
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-parquet
>            Reporter: Michael Luckey
>            Assignee: Michael Luckey
>            Priority: P2
>             Fix For: 2.35.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> ParquetIO.Parse currently does not support a Hadoop configuration.
> Although it is possible to set the configuration object, it is ignored later 
> on. Parse delegates to ParseFiles, but misses to pass the configuration 
> object here. Therefore, config is lost.
> Workaround:
> Use ParseFiles directly by unrolling Parse.expand implementation.



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

Reply via email to