bigquery

Describe the bug
If I pass 'Next 7 days' into the dateRange in query, the response is not a range over the next 7 days but only the day IN 7 days.

To Reproduce
Steps to reproduce the behavior:

1. Build a query like this:

const query: Query = {
    measures: [
      measure
    ],
    timeDimensions: [
      {
        dimension: 'Your.Dimension,
        dateRange: 'Next 7

ideally this would demonstrate projections, predicates, & tuning options like block size (using the Configuration parameter)

Problem

At present, our API documentation and API configuration in Jitsu Server contain some discrepancies. Since Jitsu API grows fast It's unavoidable. We should improve it. Clear documentation is an essential thing in OSS projects.

Solution

We should create Open API specification (yaml file) and generate both Jitsu Server handlers (gin-gonic) and doc

I am very curious about experience of newcomers with the tutorial. I am sure it can be improved to make onboarding easier.

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

At the moment we have a contributors section in each year's JSON file (2019.json, 2020.json, and 2021.json).

Should we merge these

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":

O table append deveria:

1. Checar se tabela já existe. Se não existir, levantar um erro
2. Adicionar dados via Storage.upload

Ele não deveria recriar a tabela no BQ como está acontecendo hoje.

https://github.com/basedosdados/mais/blob/8e53d1af80821f69f78780b7ef5d4cb316dbda3b/python-package/basedosdados/upload/table.py#L614