beam
Here are 219 public repositories matching this topic...
-
Updated
Jan 9, 2021 - Rust
-
Updated
Jan 1, 2021 - Erlang
-
Updated
Dec 10, 2020 - CSS
-
Updated
Nov 18, 2017 - Erlang
-
Updated
Jan 19, 2021 - C++
-
Updated
Jan 17, 2021 - Rust
In v0.9.0 we started offering --keep_intermediate_avro_files. Avro files are a great candidate for long term storage of variant data for several reasons, mainly because they can be loaded into BigQuery fast and free.
The only missing data is information in VCF header. Storing them with AVRO files will enable us to recov
-
Updated
Jan 10, 2021 - Elixir
-
Updated
Oct 7, 2020 - Python
-
Updated
Jan 5, 2021 - HTML
-
Updated
Jan 18, 2021 - Python
-
Updated
Aug 4, 2018 - Clojure
-
Updated
Oct 12, 2020 - Java
We need to add a communications section to the community page. This second would consist of sub-sections such as (but not limited to) :
- slacks
- irc
- mailing lists
- forums
Any other ideas?
Improve this page
Add a description, image, and links to the beam topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the beam topic, visit your repo's landing page and select "manage topics."
Currently
com.spotify.scio.bigtable.syntax.ScioContextOps#updateNumberOfBigtableNodesupdates all clusters for the instance.That is not desired behaviour if each cluster is dedicated for specific task - one for batch jobs, another for service, etc.
Desired API is to allow change node count for only specific cluster (dedicated for batch jobs).
Proposed API change: