Skip to content

Conversation

@ilya-kozyrev
Copy link
Contributor

@ilya-kozyrev ilya-kozyrev commented Oct 4, 2021

  1. Adding structures to manage environments that need for different parts of the app.
  • BeamEnvs contains all environments related to ApacheBeam. These will use to run pipelines
  • LogWriters contains writes for the logger. Writers should implement io.Writer interface. logging will be implemented in next PRs
  • ServerEnvs contains all environment variables that need to run the server.
  1. Adding service to manage there variables. Service operates with environment structures: ServerEnvs, LogWriters, BeamEnvs and contains methods to extract some values from os.env

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Choose reviewer(s) and mention them in a comment (R: @username).
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

ValidatesRunner compliance status (on master branch)

Lang ULR Dataflow Flink Samza Spark Twister2
Go --- Build Status Build Status Build Status Build Status ---
Java Build Status Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Python --- Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status ---
XLang Build Status Build Status Build Status Build Status Build Status ---

Examples testing status on various runners

Lang ULR Dataflow Flink Samza Spark Twister2
Go --- --- --- --- --- --- ---
Java --- Build Status
Build Status
Build Status
--- --- --- --- ---
Python --- --- --- --- --- --- ---
XLang --- --- --- --- --- --- ---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go Java Python
Build Status Build Status Build Status
Build Status
Build Status

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website Whitespace Typescript
Non-portable Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status Build Status Build Status
Portable --- Build Status Build Status --- --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests

See CI.md for more information about GitHub Actions CI.

@ilya-kozyrev
Copy link
Contributor Author

R: @pabloem @damondouglas

import "io"

// LogWriters contains writes for logger. Writers should implement io.Writer interface.
type LogWriters struct {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May we consider having a separate internal/log package? I like that we are centralizing logging and I would additionally propose enforcing structured logging. I've seen two approaches. One, using the uber zap library. Another using the native go library but logging out a struct adherent to https://pkg.go.dev/google.golang.org/cloud/logging#Entry. In the second case, just the Entry is populated and written out to stdout or stderr without using logging.Client. In GCP, structured logs are automatically parsed with the applied key/value pairs. I've used both approaches and found the second more flexible as there are settings where one just wants a single line string in the log.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've removed logs from this package and consider to implement them in a separate package in the new pr, will submit them soon :)

@ilya-kozyrev ilya-kozyrev force-pushed the BEAM-12998-Environment_service branch 2 times, most recently from cfb6ed4 to 465a5d5 Compare October 6, 2021 23:37
@aaltay
Copy link
Member

aaltay commented Oct 15, 2021

What is the next step on this PR?

@ilya-kozyrev ilya-kozyrev force-pushed the BEAM-12998-Environment_service branch from e8f495d to 2a3f274 Compare October 18, 2021 09:35
@pabloem
Copy link
Member

pabloem commented Oct 20, 2021

@damondouglas - it seems like @ilya-kozyrev addressed your comments. Is that correct?

Copy link
Contributor

@damondouglas damondouglas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pabloem LGTM

… cache and application envs

Co-authored-by: AydarZaynutdinov <aydar.zaynutdinov@akvelon.com>
Co-authored-by: daria.malkova <daria.malkova@akvelon.com>
@ilya-kozyrev ilya-kozyrev force-pushed the BEAM-12998-Environment_service branch from 980ffb3 to aa26b53 Compare October 25, 2021 15:33
@ilya-kozyrev
Copy link
Contributor Author

@pabloem rebased on master. Could you please merge it?

@pabloem pabloem merged commit 835d19a into apache:master Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants