big-data

Is your feature request related to a problem? Please describe.
Many static type checkers have issues finding Cython's stubs.
Here is from running mypy on my current project:

error: Skipping analyzing "cython": found module but no type hints or library stubs

The same issue can be seen when using import Cython as cython:

error: Skipping analyzing "Cython": found module but 

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.

This test throws NPE:

public class TestSlowAsyncMapper {
    @Test
    public void foo() {
        var hz = Hazelcast.newHazelcastInstance(newConfig());
        hz.getJet().newJob(newPipeline()).join();
    }

    private Pipeline newPipeline() {
        var p = Pipeline.create();
        p.readFrom(TestSources.itemStream(Integer.MAX_VALUE))
                .withNativeTimestamp

If the --server option is used without a protocol, then it should use https when on port 443. For example, these invocations would be equivalent, with the first one having the new behavior:

trino --server example.net:443
trino --server https://example.net:443
trino --server https://example.net

This will make the CLI consistent with the JDBC driver in this regard. While it's t

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

Could we clarify that delta-log files are JSON line-delimited files in https://github.com/delta-io/delta/blob/master/PROTOCOL.md#delta-log-entries ?

In the PROTOCOL.md file it is not clear what is the format of JSON. Every delta-log entry file is "new-line delimited json file", but this is not specified in this file. Protocol do not explicitly specify that every action is stored as a single-lin

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