Unnecessary RDD repartition if RDD is already indexed. [Improvement] about simba

[dongx-psu]

I agree with you on this ticket. It requires a physical planning strategy to handle this case. I think it would be fine to add some heuristics in SpatialJoinExtractor checking if table on one side has been indexed.

[merlintang]

since I can not fork the standalone branch, I can not send PR for this feature. Can you release the standalone version.

[dongx-psu]

How about your test on the current standalone version? Do you think it is ready to stand as the master branch?

BTW, I think you can just fork the repo and it will fork all branches for you. You just need to switch them back. If you already have a forked repo, one solution is to set the main repo as a remote and pull from it then push it back to your forked repo.

[merlintang]

We are still testing the standalone version, yes, we need to postpone this later. Yelp. The standard way like the spark, is that each dev fork the project, push to the forked project, then send PR. Because the forked version do not have the standalone version, this make a little different.

…

On Wed, Dec 7, 2016 at 4:48 PM, Dong Xie ***@***.***> wrote: How about your test on the current standalone version? Do you think it is ready to stand as the master branch? BTW, I think you can just fork the repo and it will fork all branches for you. You just need to switch them back. If you already have a forked repo, one solution is to set the main repo as a remote and pull from it then push it back to your forked repo. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABXY-boVIR7khnlviRmLemj2D5RO3gFXks5rF1PJgaJpZM4LHRPl> .