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

1 issue description
2. fix bug, enhance....
3. git commit -m "issue name (#issue number)"

Problem

At the moment, there's one configuration parameter that defines sql type of the column in DB representation of the event. This parameter is called type and is a part of mapping configuration.

Jitsu assumes that every SQL type can be used typecast and table creation both:

• CREATE TABLE (a T)
• insert $value::T

However, this assumption is wrong. One particular case i

运行示例代码，如果把user对应的age和uid属性调换一下时，即使绑定了对应的tag，但是仍然按照数据库中顺序进行赋值，数据库的第一列uid对应的了user类的第一个属性age