[
https://issues.apache.org/jira/browse/BEAM-12272?focusedWorklogId=606097&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-606097
]
ASF GitHub Bot logged work on BEAM-12272:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jun/21 18:03
Start Date: 03/Jun/21 18:03
Worklog Time Spent: 10m
Work Description: nehsyc commented on pull request #14723:
URL: https://github.com/apache/beam/pull/14723#issuecomment-854071952
> ```
> 11:31:23 Execution failed for task ':rat'.
> 11:31:23 > A failure occurred while executing
org.nosphere.apache.rat.RatWork
> 11:31:23 > Apache Rat audit failure - 2 unapproved licenses
> 11:31:23 See
file:///home/jenkins/jenkins-slave/workspace/beam_PreCommit_RAT_Commit/src/build/reports/rat/index.html
> ```
>
> I don't think I added any new dependencies, but I can see the RAT
precommit is currently failing with unapproved licenses. However, the linked
report file seems to be local on the Jenkins machine and inaccessible to me. Is
there any way I could check this?
I usually reran the failed gradle task locally and the log would be dumped
to my machine. In this case I would try running ./gradlew :rat in the working
directory.
--
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: 606097)
Time Spent: 7h (was: 6h 50m)
> Python - Backport FirestoreIO connector's ramp-up to DatastoreIO connector
> --------------------------------------------------------------------------
>
> Key: BEAM-12272
> URL: https://issues.apache.org/jira/browse/BEAM-12272
> Project: Beam
> Issue Type: Improvement
> Components: io-py-gcp
> Reporter: Daniel Thevessen
> Assignee: Daniel Thevessen
> Priority: P2
> Time Spent: 7h
> Remaining Estimate: 0h
>
> The FirestoreIO connector (BEAM-8376) for the Java SDK is currently out for
> review.
> Some of the features for the Firestore connector are new relative to the
> Datastore connector, so the Firestore team would like to add them there as
> well. Most notably the Firestore connector has a gradual ramp-up feature that
> slowly increases throughput in line with Datastore/Firestore best practices.
> Some minor adjustments to constants for batch sizing and backoff may also be
> worth looking at.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
