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 

usually, after trained model. i save model in cpp format with code:

cat_model.save_model('a', format="cpp")
cat_model.save_model('b', format="cpp")

but when my cpp need to use multi models.

in my main.cpp

#include "a.hpp"
#include "b.hpp"

int main() {
  // do something
  double a_pv = ApplyCatboostModel({1.2, 2.3});  // i want to a.hpp's model here
  double b_pv 

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.

Avoid controlling endless loop with exception in loadAnonymousClasses, e.g. by extracting loading class to the method:

  private boolean tryLoadClass(String innerClassName) {
        try {
            parent.loadClass(innerClassName);
        } catch (ClassNotFoundException ex) {
            return false;
        }
        return true;
    }

https://sonarcloud.io/project

With Hive connector

trino:default> CREATE TABLE one (a varchar);
            -> CREATE VIEW two AS SELECT * FROM one;
CREATE TABLE
CREATE VIEW

DROP TABLE is rejected on a view:

trino:default> DROP TABLE two;
Query 20210906_150832_00015_id3y3 failed: line 1:1: Table 'hive.default.two' does not exist, but a view with that name exists. Did you mean DROP VIEW hive.default.t

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

Hi Team,

I have created a vespa multinode stack and performed a load test for search query

1. search with single field with 60s timeout - median was consistent around 150 to 200ms
   endpoint : /search/
   http request : POST
   Body:
   {
   "yql":"select * from sources * where table contains "testing.vespa.search"
   }
2. search with more fields and conditions - median was 100+ secs which is very

Required by DataGrip. See crate/crate#11726

The full query is

select L.transactionid::varchar::bigint as transaction_id
from pg_catalog.pg_locks L                                                                               
where L.transactionid is not null                                                                        
order by pg_catalog.age(L