big-data

After add patch which fixes #4209 I found that sphinx emits some warnings.

+ /usr/bin/python3 setup.py build_sphinx -b man --build-dir build/sphinx
Unable to find pgen, not compiling formal grammar.
running build_sphinx
Running Sphinx v4.0.2
making output directory... done
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
building [mo]: targets for 0 po

Problem: the approximate method can still be slow for many trees
catboost version: master
Operating System: ubuntu 18.04
CPU: i9
GPU: RTX2080

Would be good to be able to specify how many trees to use for shapley. The model.predict and prediction_type versions allow this. lgbm/xgb allow this.

Remove the initial shortcut sync code in viewer/db.js for v3.1. Note that to upgrade to v3.1+ you must upgrade to v3.0 first.

There is no technical difficulty to support includeValue option, looks like we are just missing it on the API level.

See SO question

When you change a query state filter e.g. showing 'Finished' queries or 'User Error' queries, the Show Limit is not respected immediately resulting in all queries being rendered. If a re-order interval is set then Show Limit is applied on the next query refresh. If there are a large number of queries in the history this can result in the browser crashing on the first render.

The following two c

... to make it easier to read Vespa documentation on an e-reader / offline

Vespa documentation is generated using Jekyll from .md and .html files, look into options for generating the artifact as part of site generation (there might be plugins we can use here)

• Delta Lake 1.0.0
• Spark 3.1.2
• Scala 2.12
• AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)

The following code gives a NullPointerException. This is for a directory-based delta table that does not exist and uses a generated column.

import io.delta.tables.DeltaTable
DeltaTable.create
  .addColumn(
    DeltaTable.columnBuilder("value")
      .generatedAlwaysAs("true")
      .nullab

Use case:

1.) A user may want to backup all tables but no metadata like users, privileges, etc. without explicitly defining each table inside the CREATE SNAPSHOT statement.

2.) A user may want to transfer users & privileges, custom analyzers or user-defined-functions from one cluster to another without backing up a complete cluster including all data (tables).

*Feature description