spotify/scio

Verify counter behavior when mutated outside of a pipeline

Open

#1,044 opened on Feb 9, 2018

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)Scala (529 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (2,626 stars)
PR merge metrics
 (PR metrics pending)

Description

We have a feature request that metric mutation e.g. counter.inc() should fail with a meaningful message when called outside of a pipeline (a lambda).

This is probably a beam issue. We need to verify the current behavior and maybe report/fix upstream.

Contributor guide

Research direction
Test counter increment outside of a pipeline and inspect the error or behavior. Check if Beam provides meaningful error messages for this case. If not, consider filing an issue upstream.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaApache Beam
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50