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.
[SPARK-9319][SPARKR] Add support for setting column names, types #9218
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
Uh oh!
There was an error while loading. Please reload this page.
[SPARK-9319][SPARKR] Add support for setting column names, types #9218
Changes from 1 commit
3dfa4ea87f28fcf79ebf2f304f9c3bb2a8df7a51de8185f03a01cbf5f21ef8d4f5e60c96cf87fd89be0b56419cfeb59b9486d652659db9e914d08b90451b00fab710a40c77fb729f983bb5a2af45029bfe8ec2a769b9e4b3c4718897b3c8fac4118dfc27dfb40d3c67aa494a9643c49cfae9bbadc7e39949f7117046e32ecf04fdff8d93ed8d3f0433e770a6e963070e209fa2ea4a3e7767522d74ba952a930e6271d1c90f92f334b3aedca33ae7a3db11ee52804674ecfb3e7ec03866c020f7d476f43421ad8462cef1bb9cb5c73efaa4729cf56c9c34c27fd728d5c67e23b3425ff03b86f2ca233e534d188a6757446ebd6035d9d6f10aa3434572f54ff19b2e4b31ebf8b0ba9676cc1d04dc9f6fcb48680b4e753e9cee5051262d648a4ae352de02692bdb8aff36ec09e513e328b69820064e9b214ce8790ee627feafccd1df66e0fc9c73bd6f5d987df4bde289bfabf5e42d19f4fd701fb501b6a5d4411ff6ab6e0a5ace5e6a2a752ddad0b563381498dd6f81eae859dff57bdc921a94671a77488fb72634f22e86cf1a4b5cefb072ff49da7ceec76865c6b87acdf80f7b614ee0f58a5314eb9455d1d9e30c5b6974f8244010607414af6091e918fa8c83468ad0a5e31db73cc2c05eec74ba363a476bc5d6c0253e87ecf69ce1574141ac0489298211aab62bb29049f1a82f328fed3a652f6c447c9df6680cd7e9a9e61ab72b06d0ead31c80d66105732d30b706b7f741902ff0e79ef362844b69a42d9819025c4e6d730c8ba72673905b2d195e97b7080d8b50f79e48cdfb541b318c0e1b5d50a66c9b88e1d08a7a83404a28fcd17488874cd66860ea0d88a3fdc5039a4951d41e4b7720faf138cb8150f6a8a3a7c918a23368fcb57e99565c242f383789c740a9675c7e77dc9d8d61f9c8726062d20ce6f9b1f0f14e65029441431319c4e19b3d6cd3a1521b3ca5507a9da81f47f689386b6e5fc37e0701c747735cddfcfcbc536008587aedc4f14e95118350a5dba1a62724cf7a638c51d32790fe1dde39de281b873121e7821c562fa398905c0e48df33112f93e0a6cf9009175660078612c7635745e45d6e101d2fac53d81a8e046bd7024499f5f981bc41121510c5227524a395daff6c964fc19c57bc0ec2b807e71ba56529a1d327029bcdf97df2a9a6b80dd77e272d76e44e1bcf6a1a21be1b8ff688a40838a3343047969dc0e4e820ece2399b58730a37File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Since we have 4 bytes as number of records in the beginning of a page, the address can not be zero, so we do not need the bitset. For performance concerns, the bitset could help speed up false lookup if the slot is empty (because bitset is smaller than longArray, cache hit rate will be higher). In practice, the map is filled with 35% - 70% (use 50% as average), so only half of the false lookups can benefit of it, all others will pay the cost of load the bitset (still need to access the longArray anyway). For aggregation, we always need to access the longArray (insert a new key after false lookup), also confirmed by a benchmark. For broadcast hash join, there could be a regression, but a simple benchmark showed that it may not (most of lookup are false): ``` sqlContext.range(1<<20).write.parquet("small") df = sqlContext.read.parquet('small') for i in range(3): t = time.time() df2 = sqlContext.range(1<<26).selectExpr("id * 1111111111 % 987654321 as id2") df2.join(df, df.id == df2.id2).count() print time.time() -t ``` Having bitset (used time in seconds): ``` 17.5404241085 10.2758829594 10.5786800385 ``` After removing bitset (used time in seconds): ``` 21.8939979076 12.4132959843 9.97224712372 ``` cc rxin nongli Author: Davies Liu <[email protected]> Closes #9452 from davies/remove_bitset.Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.