Now insert and query share the resource ( Max Process Count control) 。 When the query with high TPS，the insert will get error (“error: too many process”). I think separator the resource for Insert and Query will makes sense. Ensure enough resource for insert。It looks like Use Yarn， Insert and Query use the different resource quota。
Or the simple way , Can we set Ratio for Insert and

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.

Please describe the problem you are trying to solve
I would like to evict entries based on their creation time. I want to evict the oldest ones first.

Please describe the desired behavior
Basically FIFO eviction. I would like to specify directly in the configuration something like:

<eviction eviction-policy="FIFO" max-size-policy="PER_NODE" size="5000"/>

**Describe alte

Feeding documents with large tensor fields (e.g tensor(p{},dt{},x[128})) using JSON or XML(deprecated) serialization is cumbersome as string representation of float/double is costing a lot of network bandwidth, storage and processing (serialize, deserialize).

Hi, if my spark app is using 2 storage type, both S3 and Azure Data Lake Store Gen2, could I put spark.delta.logStore.class=org.apache.spark.sql.delta.storage.AzureLogStore, org.apache.spark.sql.delta.storage.S3SingleDriverLogStore

Thanks in advance

Use case:
As a user I want to get a clear error message, when I try to connect to a CrateDB Cluster, that enforces TLS and doesn't allow non-ecrypted connections.

Right now I only see a message, that doesn't make this clear: e.g.:

Npgsql.PostgresException (0x80004005): 28000: No valid auth.host_based entry found for host "10.0.0.89", user "defaultuser"

Feature description

trinodb/trino#6989 introduced new BaseConnectorTest test class which replaces AbstractTestDistributedQueries and AbstractTestIntegrationSmokeTest.

Scope of this ticket is to restructure Thrift connector test code to follow new pattern.
TestThriftIntegrationSmokeTest should be merged with TestThriftDistributedQueries to form TestThriftConnectorTest

A PR