Thanks for you response. This is a little bit different. Instead of hanging at 1%, I get this error message (see image). When I look at the logs, I see two queries happening. The first is a select top 1 * from (my query) in order to define the schema, the second defines the stream (custom SQL query in full). The logs say the query executes, but the TrafactaInputStream closes after reading only 1 record. There's no error in the data-service log. The stream just closes. In the job-metadata-service log I do see that there's a request to fail job # with error message; null, but a null error message doesn't tell me what to do, so I'm not sure how to trouble shoot this. I'm not seeing the error on the SQL side, although it looks like the connection is successful, but Trifacata isn't closing it's cursors. (I can't tell for sure, still troubleshooting), but this is leaving me with suspended queries, with no blockers. Again, not positive...just guessing at this point. I'll be setting up some xevents today to monitor and try and get more information. It would just be really helpful to understand what is happening from the Trifacta side, as a null error message is difficult to interpret.
