@madAndroid was kind enough to provide instructions on how to configure Redash with Auth0/SAML on the forum: https://discuss.redash.io/t/auth0-integration/586/5.

We should port this over to the Knowledge Base (either as a section in the Authentication Options page or a dedicated one).

Raising this as a sample Beginner issue

Expected Behavior

Python unit tests should not depend on GCP service accounts being available

Current Behavior

Currently the test test_get_batch_features in the Python SDK leads to a failure when it is run from an environment where GOOGLE_APPLICATION_CREDENTIALS are not available, or it cannot infer a local Gcloud configuration. This is triggered because the Job object initiali

Need test cases to cover error handling in batch_work_executor.py

Currently, the README.md file lists all tables with their full table comment.

I'm putting a lot of info in some of my table descriptions, including SQL code blocks. These render rather badly in the comment column of the central Tables table, which treats markdown just a little different.

Perhaps the Tables table should only use the first paragraph of each table description.

E.g.

Is it mandatory to put windowing in unbounded pcollection from pubsub if i'm not using any aggregation steps i.e groupbyKey?

A note in following link is as follows.
https://cloud.google.com/dataflow/docs/guides/specifying-exec-params

**If your pipeline uses unbounded data sources and sinks, it is necessary to pick a Windowing strategy for your unbounded PCollections before you use any aggre

create_table() claims that the schema parameter is a dict, when the documentation shows it to be a list of dicts.

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

E.g. if you use the GitHub issue templates and automatically apply "bug" or "enhancement", then the bot should not (try to) relabel it.

Humans come before bots!

If the human says this is a bug, the bot should obey. (second robot law) 😆

Re: https://googleapis.dev/nodejs/bigquery/latest/BigQuery.html#createQueryJob:

It does not mention the ability to define a default dataset for the query.

However, code can do things like this:

  const query = {query: queryString};
  if (connection.datasetName) {
    query.defaultDataset = { datasetId: connection.datasetName };
  }
  // ...
  return bigquery
    .createQueryJob

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

Sometimes it is desirable to allow a workload to produce outputs which don't match the currently defined schema in BigQuery. We should plumb through setIgnoreUnknownValues as a settable hadoop confi

When using Quix along other systems to manage SQL queries, we find ourselves often copy-pasting queries to and from Quix. It could be really nice if we could integrate Quix more seamlessly with our other systems. 2 ways of doing so are:

1. Opening Quix with a link that would allow creating a new note with parameters, something like `https://quix-url/notebook/6c7c0bc-0b84-49f4-bf8a-d6fc1c6c8b4b?ne

Describe the default configuration for the application, and also the need for override for each part. eg: queue, poll time, ack timeout, thread pool size.