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.

change all x-moloch-cookies to x-arkime-cookies in tests and middleware 😋

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

In a given content cluster, using the schema, let the user easily create a selection string.

Then, add ability to run a visit using this, outputting how far into document space it is and how many documents are returned so far. This simplifies the process to develop a selection string and test it before deploying it - i.e. how many docs / fraction is kept when running the visit with the selectio

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:

This relates to crate/crate#11020

It would allow users to use the function in a default clause of a primary key column. This would enable use-cases as mentioned in the issue with libraries like dataset

This function would return text instead of uuid

"Not supported" may mean that something is not yet implemented and not yet supported. While using "not allowed" suggest that this is not allowed by the design.