The Wayback Machine - https://web.archive.org/web/20210512063701/https://github.com/topics/bigquery
Skip to content
#

bigquery

Here are 607 public repositories matching this topic...

cube.js
schoolytics-dev0
schoolytics-dev0 commented Apr 29, 2021

Describe the bug

Serverless: Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "provider.environment.CUBEJS_APP": Value not found at "self" source,
              - Cannot resolve variable at "functions.cubejsProcess.events.0.event.resource": Value not found at "self" source
            From a next major this will be
jitsu
xtreding
xtreding commented Apr 26, 2021

Problem

At present jitsucom/server supports API connectors (sources) sync only into ClickHouse and Postgres. Because it uses upsert statements. We should support all Data warehouses:

  • ClickHouse
  • Postgres
  • BigQuery
  • Snowflake
  • Redshift

Solution

  • for transactional DB (Postgres, Redshift, Snowflake): jitsucom/server should use delete (by chunk) + insert in one transaction
almanac.httparchive.org
Issue-Label-Bot

Code For The Issue Label Bot, an App that automatically labels issues using machine learning, available on the GitHub Marketplace. This is also code for the blog article: "How to automate tasks on GitHub with machine learning for fun and profit"

  • Updated Apr 23, 2021
  • SCSS
idreeskhan
idreeskhan commented Dec 30, 2019

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

SuperLSH
SuperLSH commented Apr 29, 2020

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

Improve this page

Add a description, image, and links to the bigquery topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the bigquery topic, visit your repo's landing page and select "manage topics."

Learn more