-
Notifications
You must be signed in to change notification settings - Fork 12
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
lingual-redshift doesn't seem to work and is confusing #1
Comments
This was a bug in our tutorial that's now fixed. I've also updated the docs to note that the s3cmd tool from http://s3tools.org/s3cmd is needed. if you update your tutorial it should work now (the Redshift tutorial used to be part of a different project and the sample script still referenced that by name). Our bug aside, note that you want to run the script out of it's pre-compile location of /lingual-redshift/src/main/resources/emrExample.sh not the /lingual-redshift/build/main/resources/emrExample.sh location. Let me know if you find any other issues. |
re-opening this for clarity. This is a bug report and the bug needs to be fixed; the request for direct email is just to simplify communication on a specific project. |
We will be pushing out a new version of the tutorial before end of week. Stay tuned. |
I followed the instructions under the section, 'Example Code and Detailed Installation.'
Now I tried to run the Redshift in Cascading example. First, the tutorial says, "This will build all the components needed for the examples." Then it says, "[run] the following from the cascading-jdbc base directory." So, which is it and how do I build cascading-jdbc if required? Incidentally, I executed
"./lingual-redshift/build/main/resources/emrExample.sh ..." and it gave the following error:
FAILURE: Build failed with an exception.
Project 'cascading-jdbc-redshift' not found in root project 'tutorials'.
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
The text was updated successfully, but these errors were encountered: