- 28 8月, 2019 5 次提交
-
-
由 Boyang Jerry Peng 提交于
(cherry picked from commit 075f28b7)
-
由 lipenghui 提交于
### Motivation Fix #4732 ### Modifications Add options to rewrite the namespace delimiter, disable by default Enable rewrite namespace delimiter can work well with superset: <img width="1279" alt="superset" src="https://user-images.githubusercontent.com/12592133/61385412-f0f35700-a8e4-11e9-87b2-a31b62128b58.png"> ### Does this pull request potentially affect one of the following parts: *If `yes` was chosen, please highlight the changes* - Dependencies (does it add or upgrade a dependency): (no) - The public API: (no) - The schema: (no) - The default values of configurations: (no) - The wire protocol: (no) - The rest endpoints: (no) - The admin cli options: (no) - Anything that affects deployment: (no) ### Documentation - Does this pull request introduce a new feature? (no) (cherry picked from commit 6ddd51ff)
-
由 Matteo Merli 提交于
### Motivation After the changes in #3118, there has a been a sharp increase of memory utilization for the UnackedMessageTracker due to the time buckets being created. This is especially true when the acktimeout is set to a larger value (eg: 1h) where 3600 time-buckets are being created. This lead to use 20MB per partition even when no message is tracked. Allowing to configure the tick time so that application can tune it based on needs. Additionally, fixed the logic that keeps creating hash maps and throwing them away at each tick time iteration, since that creates a lot of garbage and doesn't take care of the fact that the hash maps are expanding based on the required capacity (so next time they are already of the "right" size). On a final note: the current default of 1sec seems very wasteful. Something like 10s should be more appropriate as default. (cherry picked from commit f13af487)
-
由 lipenghui 提交于
Fixes #4734 ### Motivation "publish_time" is Pulsar SQL internal column, as Pulsar only stores timestamps, it doesn’t store the timezone information. Use timestamp as "publish_time" type is more correct way in Pulsar SQL. ### Modifications Change type of publish_time to timestamp. ### Verifying this change predicate of publish_time is pushdown Use `__publish_time__` to trim messages: ``` SELECT COUNT(*) FROM "sql-test-1" WHERE "__publish_time__" >= TIMESTAMP '2019-07-18 17:26:50.119' AND "__publish_time__" < TIMESTAMP '2019-07-18 17:26:51.119'; ``` ![image](https://user-images.githubusercontent.com/12592133/61447301-43835080-a983-11e9-814b-bc2b378f02b9.png) Without `__publish_time__` predicate: ``` SELECT COUNT(*) FROM "sql-test-1"; ``` ![image](https://user-images.githubusercontent.com/12592133/61447427-82190b00-a983-11e9-8d3f-3bf2a4798047.png) (cherry picked from commit 6f5416ee)
-
- 16 4月, 2019 1 次提交
-
-
由 Boyang Jerry Peng 提交于
* Adding offloader support for sql * cleaning up * cleaning up imports * cleaning up configs * fix imports * fix behavior when offloader not configured and fix license * fix unit test
-
- 12 2月, 2019 1 次提交
-
-
由 Matteo Merli 提交于
-
- 07 12月, 2018 1 次提交
-
-
由 Matteo Merli 提交于
-
- 25 8月, 2018 2 次提交
-
-
由 Boyang Jerry Peng 提交于
### Motivation Improve error message handling in presto pulsar connector
-
由 Boyang Jerry Peng 提交于
* allow predicates concerning publish time to push down to pulsar * cleaning up
-
- 07 8月, 2018 1 次提交
-
-
由 Boyang Jerry Peng 提交于
* adding module for Pulsar SQL * renaming presto pulsar package * fixing pom and configs * fixing pom * using project version variable in pom * adding comments
-