forked from heavyai/heavydb
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update #32
Merged
Merged
update #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o the Planner so Expr::collect_column_var can work as named.
We have to use a consistent columnar cache for an entire query.
…olumn_calculations Move column metadata calculations out of per-row loop in import_thread delimited
This reverts commit d5a80144e563cdf6b1085ea54edd11bf857f44cf.
ResultRows was being used as a catchall for small inline includes across a few QueryEngine files. Split those includes out to their relevant files and move the ResultRows reduction routine (for interleaved bins layout) into ResultSetStorage with the rest of the reduction routines.
Also adds key_for_string function, returning the dictionary ID of a dictionary encoded string.
\d reports the shard_count stored in meta * (size of cluster -1), usually cluster contains aggregator, leaves, and string dictionary server. Correcting the count in this PR.
* Add new shared function to get the current stack trace as a string * Make exception-safe, per Pavan * Even neater, per Pavan
Replace CHECK with a throw so that the row is tossed instead of crashing
… other code paths.
* Add a script to find anomalies in benchmark results of two branches * Update benchmarks README add comparison script instructions
Revised binding SQL operators to extension functions.
In a single node setup, the distance would be minimum of device_count or difference of device_count - shard_count. For example: If a single node server running on 3 devices a shard column has values 0 to 9 in a table with 4 shards, device to fragment keys mapping would be: device 1 - 4,8,3,7 device 2 - 1,5,9 device 3 - 2, 6 The bucket value would be 4(shards) - 3(devices) = 1 i.e. minimum of device_count or difference.
Folly has some dependencies on openssl, which have caused issues when static linking with the upcoming deps upgrade. Explicitly linking to openssl when pulling in folly should resolve this.
Warning now occurs on GCC 9
…columnar output) * Centralize where we allow using logical columns sizes in QMD * Use a column-aware byte size for allowed queries * Add support for 2/1-byte reduction of non-agg columns * Properly set the logical size when there is a mismatch in type between an agg and its argument * Add proper agg_min_ and agg_max_ functions for 16/8 bit aggregates * Add 16/8-bit min/max reduction for the result set. * Fix the mismmatch between argument types with COUNT and non-encoded string args * Relax result set's reduction CHECKs to work with columnar SAMPLE * Add proper 32/16/8 bit slotEmptyKeyCAS functions. * Refactor codegen for SAMPLE in TargetExprCodegenBuilder * Enable using 32/16/8 bit slotEmptyKeyCAS functions in code generation * Add tests to properly cover less than 32-bit aggregates.
It doesn't make sense to highlight these low-level examples now that pymapd exists. Users shouldn't be writing Thrift code or needing to use JDBC via python
* Fix overflow in the translated null value. * Avoid overflow in deciding the baseline group by.
Exception is added to ensure that user is unable to create a high precision timestamp column with fixed/ encodings
No longer required as this no longer includes any CE components.
Also updating README to remove references to Immerse
…hit-testing enabled. * Auto-injects up-to 3 rowid columns into the RA tree right before render query execution. This is enabled via a "enableHitTesting" vega data property.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.