Various SQL, api and context functionality adds #130
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
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.
This pull request includes:
StructTypecreationThe last one I might need your help. I broke it out into a separate namespace since it seemed to need its own or I thought you might specifically have a place for it. I also thought you'd end up wanting to refactor it quiet a bit.
The idea here is that you only get one Spark context per JVM, so might as well store it in an
atomand keep it around without having to create it over and over. This esp. true since most of the initial configuration (expect the app name, which I'm open for suggestions) can be derived from the JVM environment (i.e. properties etc).