#183: Updated user guide to include latest changes #184
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
kaklakariada
requested changes
Jul 13, 2023
| To use the connector, we assume you have an Exasol cluster running with a | ||
| version `6.0` or above. Similarly, you have a Spark cluster running with a | ||
| version `2.3.0` or later. | ||
| The Spark Exasol connector has two variants, one for using with Exasol `JDBC` sub-connections and one for using with AWS `S3` as intermediate storage. |
There was a problem hiding this comment.
Not sure if users know the differences of the two variants. Maybe shortly explain their advantages/disadvantages or recommendations when to use which.
Co-authored-by: Christoph Pirkl <[email protected]>
|
Kudos, SonarCloud Quality Gate passed! |
kaklakariada
approved these changes
Jul 13, 2023
morazow
added a commit
that referenced
this pull request
Jul 14, 2023
* #150: Added S3 intermediate storage layer (#152) Co-authored-by: Christoph Pirkl <[email protected]> * #149: Added s3 import query generator and runner (#156) Fixes #149 Co-authored-by: Christoph Kuhnke <[email protected]> Co-authored-by: KK <[email protected]> * #160: Add support for writing to Exasol database using S3 as intermediate storage (#161) Fixes #160 * Address review suggestion from @tkilias * #159: Added cleanup process to remove intermediate data after job finish (#165) Fixes #159 --------- Co-authored-by: Christoph Kuhnke <[email protected]> Co-authored-by: KK <[email protected]> * #158: Refactored options class (#167) Fixes #158 --------- Co-authored-by: Torsten Kilias <[email protected]> * #168: Refactored to add module setup (#170) Fixes #168 * #171: Refactored artifact packaging and releasing process for module setup (#173) --------- Co-authored-by: Sebastian Bär <[email protected]> * #174: Refactored GitHub workflow actions (#175) Fixes #175 * #176: Fixed sha256sum files upload bug (#179) * #155: Refactored to unify user parameters (#178) Fixes #155 --------- Co-authored-by: Christoph Pirkl <[email protected]> * #164: Added validation check before writing to intermediate location (#180) Fixes #164 --------- Co-authored-by: Christoph Pirkl <[email protected]> * #162: Updated developer guide with staged commit behaviour (#182) Fixes #162 --------- Co-authored-by: Christoph Pirkl <[email protected]> * #183: Updated user guide to include latest changes (#184) Fixes #183 --------- Co-authored-by: Christoph Pirkl <[email protected]> * Updated version to `2.0.0` (#185) * Changed version * Improved default options * Updated changes and user guide docs --------- Co-authored-by: Christoph Pirkl <[email protected]> Co-authored-by: Christoph Kuhnke <[email protected]> Co-authored-by: KK <[email protected]> Co-authored-by: Torsten Kilias <[email protected]> Co-authored-by: Sebastian Bär <[email protected]>
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.
Fixes #183