Currently com.spotify.scio.bigtable.syntax.ScioContextOps#updateNumberOfBigtableNodes updates 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:

- def updateNumberOf

The functions in this file should be factored out to a separate utility lib as they are reused in bitcoin-etl https://github.com/blockchain-etl/ethereum-etl/blob/develop/ethereumetl/misc_utils.py

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

• base.html - @tymosh
• base_chapter.html - @tymosh
• error.html - @tymosh

2020

• base.html - @tymosh
• contributors.html - @tymosh
• [x]

Over time we've had some things leak into the diff methods that make it more cumbersome to use BigDiffy via code instead of CLI.

For example diffAvro here https://github.com/spotify/ratatool/blob/master/ratatool-diffy/src/main/scala/com/spotify/ratatool/diffy/BigDiffy.scala#L284

User has to manually pass in schema otherwise we they receive a non-informative error regarding null schema, add

As far as I can tell, these functions are completely unused and can be removed:

• https://github.com/pydata/pandas-gbq/blob/9fb246469af2972db0052522f5000cdafee41b4c/tests/system/test_auth.py#L14
• https://github.com/pydata/pandas-gbq/blob/9fb246469af2972db0052522f5000cdafee41b4c/tests/system/test_auth.py#L39

@medvedev1088
Hi,
I found that there ara two kinds of output in transactions.json.
One is nonstandard, and the other is pubkeyhash.
I thought the nonstandard output is the op_return output, but i found outputs of many (not all ) coinbase txs also are nonstandard. And address of miner is like“nonstandard3318537dfb3135df9f3d950dbdf8a7ae68dd7c7d”.
Here is an example:
transaction: {
"hash":

Stencil points to a server which holds file descriptors for the protobufs. We could add doc/script to setup a SimpleHTTPServer for the given protobufs.

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