When a user wants to stream data to a date-partitioned BQ table, the way to do this is:

//noinspection ScalaStyle
class DayPartitionFunction()
  extends SerializableFunction[ValueInSingleWindow[TableRow], TableDestination] {
  override def apply(input: ValueInSingleWindow[TableRow]): TableDestination = {
    val partition = DateTimeFormat.forPattern("yyyyMMdd").withZone(DateTimeZo

In the following file:
https://github.com/feast-dev/feast/blob/master/infra/charts/feast/values-batch-serving.yaml

stores:
      - name: historical
        type: BIGQUERY
        config:
          project_id: <google_project_id>
          dataset_id: <bigquery_dataset_id>

If you provide the actual dataset_id, which is in the format of project:dataset_name feast will not able

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

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

Right now, traffic to almanac.httparchive.org (no file path) is redirected to the 2019 landing page.

Let's redirect that traffic to the 2020 landing page to make readers aware that 2020 is on the way and start generating interest/anticipation. We don't need to promote the exact release date yet, because we'll make a big announcement when it's ready.

This should be a simple config change to t

@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.