Skip to content
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

Merge from master #1

Merged
merged 587 commits into from
Jun 27, 2017
Merged

Merge from master #1

merged 587 commits into from
Jun 27, 2017

Conversation

madhurkumar
Copy link
Owner

No description provided.

Elon Azoulay and others added 30 commits June 6, 2017 10:00
If the current and new values are the same do not set jmx export otherwise an exception is thrown.
Expose elements in the queue via an iterator.
Added 2 new properties to the resource groups: queuedTimeLimit and runningTimeLimit.
Allow repeating an element for a given number of times. The return
result is an array.
Add array aggregation benchmark to measure the performance for
double-typed array aggregation. Extend the ablility of
AbstractOperatorBenchmark to expose peak memory usage.
Make BlockBuilderStatus nullable in various block builders to reduce
the memory usage for functions that aggregate columns into complex
types; e.g., array_agg, map_agg, histogram, min_by, etc. In theory,
the change can reduce memory utilization up to 43%, which is the ratio
of the size of BlockBuilderStatus over the size of BlockBuilder. In
practice, we may observe a memory safe around 25 - 30% for large scale
of data.

Small-scale benchmark for array_agg on double type:
before: sql_double_array_agg ::   33.493 cpu ms :: 3.13MB peak memory
after:  sql_double_array_agg ::   33.414 cpu ms :: 2.33MB peak memory

Large-scale benchmark for array_agg on double type:
rows    memory (before)  memory (after)  save
20 M    4.79 GB          3.50 GB         27%
30 M    7.53 GB          5.64 GB         25%
40 M    9.86 GB          7.03 GB         28%
The thee last test cases in
TestTransformExistsApplyToScalarApply#testDoesNotFire
do not differ much and there is not much sense to keep them all.
This commit removes two of them.
LateralJoin is preferred to be used in case of scalar subqueries.
Returning only input properties for apply node is incorrect as it does
not consider subquery properties.
AddLocalExcanges is using PropertyDerivation classes which do not
support subquery related plan nodes like ApplyNode.
nonReserved cannot contain recursive rules.
The mechanism for handling non-reserved keywords relies on being able to
intercept the parsing operation and replacing the nonReserved entry in the
parse tree with an IDENT token.

Modifying the tree in this manner breaks when dealing with intermediate
nodes, presumably due to how enter/exit rule notification is weaved into
the traversal/building of the tree.
We need to allow '.' in resource group name for backward compatibility,
so '.' cannot be used as delimiter to parse '.' separated segmented name.
ArturGajowy and others added 29 commits June 23, 2017 07:38
Make Util.pruneInputs return Optional<Set<Symbol>>, rather than
Optional<List<Symbol>>, because for most nodes we're thinking about sets
of used symbols, rather than the ordering of the output symbol list.

In two specific cases, ValueNode and TableScanNode, retain the previous
ordering explicitly, rather than losing it in the set, to avoid making
superfluous changes to the node during optimization.  The
PruneJoinColumns rule was already retaining the order of its outputs,
and this patch does not affect that behavior.
The Travis builds hang on TestHiveTableStatistics with the new images.

https://blog.travis-ci.com/2017-06-21-trusty-updates-2017-Q2-launch
If page.getSizeInBytes() is zero, the page may not be returned to the client.
The only known case when this happens is if the page contains only SliceArrayBlocks
and all values are null.
After executing a schema-altering query such as CREATE TABLE,
datastax driver waits for a certain time period for "schema
agreement", before refreshing the schema. The default timeout
is 10 seconds, which might be low for schema changes to be
propagated to all the nodes.
to account for the fact that it may take some time for the
schema metadata to be refreshed. This is similar to the retry
mechanism that was added to assertContains() method. Hopefully
this will fix the intermittent test failures.
The Hive connector lists partition names during planning, then fetches
metadata separately while generating splits. The latter can fail if
the partition is dropped in between the two metastore calls.
Detect the MySql error ER_TRANS_CACHE_FULL and generate an
additional error message.
@madhurkumar madhurkumar merged commit dcc11c9 into madhurkumar:master Jun 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.