- - Knowledge base
Product Updates
Events

30-Day Free Trial: It’s Never Been Easier To Get Started With StreamSets

4 months ago

Home
Community overview
StreamSets Platform

StreamSets Platform

Get inspired and gain all the knowledge you need

1088 Topics

Recently active

Most replies Most views Newest first

paulStreamSets Employee

posted in Community Articles and Got a Question?

SDC 5.7.x - Orchestration pipeline calling a Job Template does not function properly

Environment:StreamSets Data Collector (SDC) 5.7.0 & 5.7.1 An orchestration pipeline which uses Start Jobs stages The orchestration stage starts a job using a Job Template The orchestration stage is configured with the Run in Background setting disabled Issue:In StreamSets Data Collector (SDC) 5.7.0 and 5.7.1, orchestration pipelines that use a Start Jobs stage to start a job using a Job Template do not function properly when Run in Background is disabled. With this configuration, the pipeline should wait for the job to complete before moving to the next stage, but instead the pipeline starts the job and immediately moves on, which can cause unexpected results for downstream jobs. Resolution:There is a fix planned for this issue in the SDC 5.8.0 release. In the short term, if your organization has an active support contact, you can contact StreamSets Support to obtain a patch to resolve the issue.

1 month ago

AkshayJadhavStreamSets Employee

posted in Share your Best Practices

SDC 5.7.X is not honouring the proxy configurations.

Environment:Streamsets Data Collector 5.7.X Proxy Configurations. Issue:There seems to be an issue with the latest version of the data collector (5.7.x). Specifically, it has come to our attention that the "http.nonProxyHosts" configuration is not being honored. Additionally, when executing the "ps -ef | grep sdc" command on the Linux host, the Java configurations are not visible. Solution:There is an issue with the data collector where proxy configurations are not working and will be fixed in further version(will keep updating the article once we have the exact fix version).The alternative/workaround is to just set it in the “Advanced Java Options” panel:-Dhttp.nonProxyHosts='*.azuresynapse.net'Any JVM configs specified directly will override those configurations and you could confirm by running “ps -ef | grep sdc” command on the Linux machine where data collector is running. NOTE: We have made some changes in latest version of data collector not to expose the proxy configuration hen

1 month ago

paulStreamSets Employee

posted in Community Articles and Got a Question?

john.mcavoyStreamSets Employee

asked in Community Articles and Got a Question?

Kafka Stage fails with error "Request joining group due to: rebalance failed due to 'null' (DisconnectException)"

IssueA Kafka stage fails to connect to the broker due to the follow error stack trace:INFO ConsumerCoordinator - (Re-)joining groupINFO NetworkClient - Disconnecting from node xxx due to socket connection setup timeout. The timeout value is 8424 ms.INFO ConsumerCoordinator - Group coordinator is unavailable or invalid due to cause: null. isDisconnected: true. Rediscovery will be attempted.2023-09-27 13:07:58,776 INFO ConsumerCoordinator - Request joining group due to: rebalance failed due to 'null' (DisconnectException)BackgroundThis specific Kafka Client exception appears when the Kafka Client’s socket-connection-setup-timeout-max-ms is set too low, causing it to attempt to re-join the group.The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. SolutionWhen this property is set too low, the Kafka Client will time out during the

1 month ago

Sankar ArunachalamFan

posted in Share your Best Practices

Cloud DB migration - query

Can we configure multiple tables in same pipeline when we use JDBC Query consumer 1 as origin and JDBC producer 1 as destination. in my case i need to send 20 tables data to send from on-premise DB (db2) to cloud DB (Azure postgresql)?. i am thinking to avoid multiple pipelines creation in streamsets.

1 month ago

shivrajFan

asked in StreamSets Academy

Facing an error while testing a pipeline on STF 5.x

We are facing some connection issue from STF side while executing a test code, that might be regarding the organization ID not sure why this issue is occurring it saying for organization the url STF calling is “api/security/v3/orgs/e4cbaa88-611a-11ed-b310-c96332d26f9a” but url must be ”http://api/security/v3/orgs/e4cbaa88-611a-11ed-b310-c96332d26f9a?”. I’m not sure how to fix this Error. E requests.exceptions.MissingSchema: Invalid URL

1 month ago

alejandro.alfonsoStreamSets Employee

asked in Share your Best Practices

Snowflake JDBC Driver v3.13.25 Behavior Change and SNOWFLAKE_11 Error

Error: If your Snowflake account name contains underscores and you're using Snowflake JDBC driver version 3.13.25 or higher, you might encounter the following error message:SNOWFLAKE_11 error. This error message indicates a communication problem with the message: "JDBC driver encountered a communication error. Message: Exception encountered for HTTP request: my-account.us-west-2.privatelink.snowflakecomputing.com: Name or service not known."Solution: To prevent this error, explicitly set allowUnderscoresInHost to 'true' in your JDBC connection string or properties. Refer to the Snowflake Community article for additional guidance.Affected Environments: This issue impacts environments meeting the following criteria:Snowflake account name contains underscores. JDBC is used for private link connections via the 'classic' regioned URL (e.g., https://my_account.us-west-2.privatelink.snowflakecomputing.com). Upgrading Snowflake JDBC driver from version 3.13.24 or lower to 3.13.25 or higher.

1 month ago

Arti_RichhariyaFan

asked in Share your Best Practices

Reading File from s3 and saving it as a same name

I am reading a file from s3 and after doing some manipulation in file i wanted to save it different location in s3 but with same name .how can i do this?please help.

1 month ago

paulStreamSets Employee

posted in Community Articles and Got a Question?

StreamSets Control Hub rpm package for Red Hat Enterprise Linux 8

QuestionThere are rpm packages for Red Hat 6 and 7, but not for Red Hat 8? AnswerStreamSets has tested the RHEL 7 package on 8 and certified it for use. There are no plans to release a separate rpm package specifically labeled for RHEL 8.

1 month ago

Priya151997Fan

asked in Community Articles and Got a Question?

After S3 Event need to capture file name in expression evaluator

Hi All,we are new in streamsets !!In our usecase we are uploading file in s3 which predefined name as abcd_sggshs_31-04-2018.csvwe need to capture this above parameter which are in our file name,we are generating events after uploading file in s3,using expression evaluator we are trying to capture this parameter in json file in s3.but we are not getting desired output.below are the expression we are using please suggest the correct expression to get the file name.

1 month ago

somFan

asked in Community Articles and Got a Question?

Jobs do not carry over offset value when migrate from one server to another.

The offset is always stored in the Control Hub (SCH). The Data Collector (SDC) stores the offset to the offset.json file and sends the information to the SCH periodically. When 'Enable Failover' is checked, the offset is migratable i.e the SCH can start a job on a different SDC (SDC_2) with the last-saved offset (from the previous SDC - SDC_1, which is not available anymore). If 'Enable Failover' is not checked, the offset is tied to a specific SDC ID and it does not migrate i.e the SCH cannot start a job with the last-saved offset from another SDC (SDC_1) on a different SDC (SDC_2). On a new SDC, the job will run the pipeline from the beginning. Failover needs to be enabled for the offset to be migrated.

1 month ago

kushal_upadhyayFan

asked in Community Articles and Got a Question?

Reading avro file from a bucket similar to S3 and trying to convert into parquet

I am reading an avro file from a custom cloud similar to S3 and trying to conver it into parquet file using whole file evaluator but its giving an error Record1-Error Record1 CONVERT_01 - Failed to validate record is a whole file data format : java.lang.IllegalArgumentException: Record does not contain the mandatory fields /fileRef,/fileInfo,/fileInfo/size for Whole File Format. : (View Stack Trace...

1 month ago

gccoulterStreamSets Employee

posted in Community Articles and Got a Question?

Converting an AVRO file (with Schema) to Parquet, using Whole File Transformer

Here we will be covering how to convert an AVRO file with Schema, to a Parquet file.STEP 1Set your pipeline up as follows;Directory - Whole File Transformer - Local FS STEP 2Configure your Directory Origin as follows; GENERAL TAB FILES TAB Please ensure you make the amendments necessary to certain fields to suit your own set up, e.g. File Name Pattern. Keep the rest as in the screenshot. POST PROCESSING TAB DATA FORMAT TAB STEP 3Configure Whole File Transformer stage as follows; GENERAL TAB JOB TAB*amend file directory as necessary AVRO TO PARQUET TAB If you preview the pipeline, ensure to select the following boxes, which will allow you to click in to each record and schema; You should now have a .parquet file from your original AVRO.

1 month ago

skyRoadie

asked in Community Articles and Got a Question?

Produce Events Error

When I am testing the Produce Events of a component. When I uncheck the "Produce Events" box, the component configuration displays normally. However, when I check it, I always encounter the following error. Do you know what might be causing this? Has anyone else experienced this issue?

1 month ago

nathanStreamSets Employee

posted in Community Articles and Got a Question?

Technical Service Bulletin 2023-08-25 (TSB) - Azure Synapse, Delta Lake, Google BigQuery, and Snowflake destinations issues with DateTime data

StreamSets Support team would like to inform you of an issue where StreamSets Data Collector pipelines using destinations such as Azure Synapse, Delta Lake, Google BigQuery, or Snowflake might corrupt the data for the DATE/DATETIME/TIME fields.Products Affected: StreamSets Data Collector Releases Affected: StreamSets Data Collector 5.6.0 and prior versions Users Affected: StreamSets Data Collector pipelines using Azure Synapse destination, Delta Lake destination, Google BigQuery destination, and Snowflake destination. Severity: High Description: It has been identified that in some cases, DATE/DATETIME/TIME datatype fields could be corrupted. Users could be finding that their DATE/DATETIME/TIME data fields contain incorrect dates. This issue happens only if all the following conditions take place:The pipeline writes to one of the following stages: Azure Synapse destination Delta Lake destination Google BigQuery destination Snowflake destination. The pipeline writes to multiple tab

1 month ago

nathanStreamSets Employee

posted in Community Articles and Got a Question?

Technical Service Bulletin 2023-07 (TSB) - Changes in Amazon S3 Stage Properties from StreamSets Data Collector version 5.6.0

StreamSets Support Team would like to inform you that starting with Data Collector 5.6.0 pipelines with Amazon S3 stages fail to execute if the "Bucket" or "Bucket and path" property contains a forward slash (/). Products Affected: StreamSets Data Collector Releases Affected: Starting from StreamSets Data Collector version 5.6.0 Users Affected: StreamSets Data Collector pipelines that include the forward slash (/) in the bucket property of Amazon S3 stages. Severity: Medium/High Description: Starting with version 5.6.0, you can no longer include the forward slash (/) in the following properties for Amazon S3 stages due to an Amazon Web Services SDK upgrade:Bucket property for the Amazon S3 origin Bucket and path property for the Amazon S3 destination and executorAdditional details regarding this change can be found in the Upgrade Impact documentation.Immediate action required: YesResolution: Avoid using the forward slash (/) in the bucket name as this may cause signature mismatch error

1 month ago

nathanStreamSets Employee

asked in Community Articles and Got a Question?

Technical Service Bulletin 2023-09-01 (TSB)- Thread Leak In Snowflake Stages

StreamSets Support Team would like to inform you of an issue where StreamSets Data Collector pipelines using Snowflake stages might have problems with threads not being released. Products Affected: StreamSets Data Collector Releases Affected: StreamSets Data Collector version 5.6.0 and 5.6.1 Users Affected: StreamSets Data Collector pipelines using Snowflake stages. Severity: High Description: A minor thread leak has been detected in all the Snowflake stages. If a user environment involves a substantial number of Snowflake pipelines, users may observe this thread leak behavior, which can impact the overall system performance and resource utilization.Immediate action required: Yes, upgrade to SDC 5.6.3 or 5.7.X.Workaround: NoneResolution: Fix for this issue has been included in SDC 5.6.3 and 5.7.x release. For your questions, please contact our Support Team via our Support portal or at support@streamsets.com.

1 month ago

nicholas.mendozaFan

posted in Community Articles and Got a Question?

Underscore in account name can cause SNOWFLAKE_11 error

When trying to connect to Snowflake in SDC, you may encounter the following error:SNOWFLAKE_11 - Could not create SQL DataSource: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: JDBC driver encountered communication error. Message: Exception encountered for HTTP request: Remote host terminated the handshake.This error may be caused by some configuration mistakes in the stage. One possible cause is underscore(s) in the account name. The Snowflake JDBC driver does not support the use of underscores in URLs, which include the account name. If your account name does contain underscores, and you are receiving a similar error, a workaround would be to use a hyphen instead.

1 month ago

himanshu1234567Discovered Fame

asked in Community Articles and Got a Question?

ImportError: cannot import name 'JSONDecodeError' from 'requests.exceptions'

while running python program using streamsets python sdk we are getting error File "/var/lib/jenkins/.local/lib/python3.8/site-packages/streamsets/sdk/exceptions.py", line 5, in <module> from requests.exceptions import HTTPError, JSONDecodeError ImportError: cannot import name 'JSONDecodeError' from 'requests.exceptions'we have found solution for this but we want to know why we are getting this error.Solution for this is manually we are replacing line “from requests.exceptions import HTTPError, JSONDecodeError” with “from json import JSONDecodeError”

1 month ago

Sankar ArunachalamFan

asked in Share your Best Practices

Cloud DB migration - query

1 month ago

LavenderStreamSets Employee

asked in Share your Best Practices

Pipeline Finisher shows error Unsatisfied precondition(s) '${record:eventType() == 'no-more-data'}'

Issue: Pipeline can run successfully but Pipeline Finisher stage shows error “Unsatisfied precondition(s) '${record:eventType() == 'no-more-data'}'”Resolution:This error is due to the configuration in Pipeline Finisher stage, On Record Error tab as Send to Error. Therefore, this error COMMON_0001 - Stage precondition: CONTAINER_0051 - Unsatisfied precondition(s) '${record:eventType() == 'no-more-data'}' is an expected behavior. In this case, the pipeline would still end when it receives no-more-data event, but it would keep generating these error records until no-more-data condition is met.To get rid of this error, you can change in On Record Error tab from Send to Error to Discard. You can read more about this configuration in our documentation: Stopping a Pipeline After Processing All Available Data.

1 month ago

alejandro.alfonsoStreamSets Employee

posted in Share your Best Practices

Legacy Control Hub & SAML - WEB_SSO_204 error

Problem:When attempting to log in to Legacy Control Hub with SAML enabled, users encounter an HTTP 401 error after trying to authenticate with the Identity Provider. The Login Audit trail provides the following information:HTTP Status Code: 401 Error Type: WEB_SSO_204 Response Status: urn:oasis:names:tc:SAML:2.0:status:RequesterSolution:The above error basically means that the Identity Provider has not granted authorization to the user, resulting in a 401 error response to Legacy Control Hub.This issue may stem from a misconfiguration of SAML settings between Legacy Control Hub and the Identity Provider. In most cases, the problem is related to the SAML keys used by Control Hub. Ensure that the public keys are valid and that the Identity Provider is utilizing the same keys. We recommend exchanging fresh copies of metadata and public keys between Legacy Control Hub and the Identity Provider. Afterward, clear your browser's cache and attempt to log in to Control Hub again. If you encount

1 month ago

Page 2 / 44

Badge winners

Sanjeevhas earned the badge Eager to help
AkshayJadhavhas earned the badge Eager to help
john.durkinhas earned the badge Eager to help
samhas earned the badge Eager to help
saleempothiwalahas earned the badge Eager to help

Show all badges

Terms & Conditions

Sign up

Already have an account? Login

Social Login

Username *

E-mail address *

What I do... *

Data Leader Data Architect Data Engineer Data Scientist Other

Company *

Country *

Zip Code *

Marketing Communications

Yes No

Password *

I have read and Agree to the Website Terms of Service and I have read and acknowledged the Privacy Policy.

loginBox.register.email_repeat

Login to the community

No account yet? Create an account

Social Login

Username or Email

Password

Remember me

Forgot password?

Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.

Username or e-mail

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.