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

It would be great to have FBeta, F2, or F0.5 metrics to be implemented without the need for a custom metric class defined by user.

catboost version: 0.26

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

Currently we are able to map schemas and tables using file based mapping. This is great as it makes it possible to handle the case where schemas and tables names differ with casing only. However we do not support this for columns yet. So in case user has a table where two column names differs with casing only (like column A and a) we are not able to read it.

See `io.trino.plugin.jdbc.mappin

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

Hi,
I am running the deltaTable = DeltaTable.convertToDelta(spark, f"parquet.{data_path}") to read a DeltaTable from the parquet files but it doesn't return one as suggested in the documents. However, it successfully converts them. If I read them exactly after that line again using forPath, it will give me the DeltaTable.

![image](https://user-images.githubusercontent.com/3591686/12765840

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