Community Articles and Got a Question?

The Issue:  When attempting to create a Connection for an Azure account, you receive the following error message: ADLS_02 - Failed to connect to Azure Data Lake Store: ‘Operation failed: “An HTTP header that’s mandatory for this request is not specified”,400,PUT, <URL>The Solution:  This error could potentially indicate that the Connection type set in Control Hub and the Azure account type do not match. When using a Data Collector version that is higher than 5.4, you are presented with a number of options when creating a new connection to Azure. These options include: Azure Blob Storage Azure Data Lake Storage Gen2 Azure Synapse When this error is encountered, before troubleshooting further it is important to first check that the connection type that was chosen here matches the Azure Account type you are connecting to. This can be verified by checking the Azure Account FQDN. For example: An FQDN like example.dfs.core.windows.net would be used for an Azure Data Lake Storage Gen2 c

Hi Team, I have paid for white belt certification and received a receipt number as well with payment confirmation for white belt exam.I never received any email from ProctorU which consists of code that I need to enter to proceed to schedule an exam. It’s been 15 days now.Can anyone help on how to proceed with this issue? Thanks,

I am using the python SDK and I when I use the method “.committer” or “.last_modified_by” on a pipeline object, I am expecting to get back an email that I am able to see under “Committed By” on the platform. However, I get back a long string that I can’t make out:sudo code of what I am doing: sch = ControlHub(credential_id="cred_id,token = token)print(sch.pipelines.get(commit_id = commit_id).last_modified_by) and instead of getting a string of an email returned, I am getting something like this returned:a83b3195-61f4-11ee-a6e4-…..@b5f95dcd-5f00-11ec-b405-…… Would you happen to know how I can turn this string into a valid email? I couldn’t find anything on this topic in the docs.  

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

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.

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.   

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.

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...   

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.

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?  

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

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

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.

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.

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”

Upgrading one or both of the backend databases for SCH 3.x (relational database and timeseries database) has no effect on SCH itself assuming that you are upgrading to a supported version of the database. You will need to either bring down SCH during the upgrade, or put the database into read-only mode, and of course take a backup of the database before beginning the upgrade.In a scenario where a subsequent rollback of the database to the backed-up version is contemplated, be aware that there will be some data loss, even if there were no new jobs created or other changes made (code freeze). Some of this data includes, but is not limited to:Any clean up of the DB Writing to InfluxDB Writing to the PostgreSQL Timseries DB (job metrics that don’t go to InfluxDB but to the SQL DB) Updating jobs statuses Running scheduler tasksThese data would need to be manually reconstructed from the upgraded database and backported to the rolled-back database.If you have any additional questions, please

In SDC versions up to 5.5.x, you may see CONTROL_HUB_API_00 errors which can cause pipelines and jobs to fail. There is no context in the logs as to what was happening that led up the to the error; it’s just a generic error that occurs when any type of API call to SCH fails.In SDC 5.6.x, this error was removed and more helpful logging was added that captures the specific API call that was being made and what the exception was. If you are encountering the CONTROL_HUB_API_00 error in an older version of SDC, StreamSets Support recommends either upgrading to at least 5.6.x, or install SDC 5.6.x or higher in a non-production environment and reproduce the issue. This will allow StreamSets Support to more effectively assist you and find the root cause of the issue.

IssueAfter upgrading MapR client libraries or applying a MapR client patch on an SDC node, pipelines using Hadoop stages fail with some Provider could not be instantiated error or ClassNotFoundException at startup, indicating some Hadoop class cannot be found within the Java classpath.BackgroundDue to licensing restrictions, StreamSets cannot distribute MapR libraries with Data Collector. As a result, you must perform additional steps to enable the Data Collector machine to connect to MapR.When the bin/streamsets setup-mapr prerequisite is completed, SDC creates symlinks to the installed MapR Client libraries on the system in the streamsets-libs/streamsets-datacollector-mapr-version-lib/lib directory.When applying a MapR Client patch or upgrading the MapR Client package on the SDC machine, some JAR files in the MapR client installation patch will be renamed which will cause broken symlinks within SDC’s MapR stage library directory.SolutionThe Provider could not be instantiated exceptio

I have a field mapper to remap camel case fields to snake case. This is the message i am trying to save:{   "id": "e35fd529-613f-5e79-036f-f37c2801041d",   "batchName": "SIT Axle3+ 9_12_test",   "batchSize": 35,   "numberOfAudited": 35,   "batchType": "TRIP_BASED",   "batchMode": "RANDOM",   "batchFacility": "71",   "batchDirection": "West",   "batchPlaza": "",   "batchLane": "",   "fromTimestamp": 1694538060,   "toTimestamp": 1694566800,   "createdTimestamp": 1694626323,   "createdBy": "mmccammon@etcc.com",   "completedTimestamp": 1697039389,   "completedBy": "asayed@etcc.com",   "auditDetailList": [      {         "id": "a4f274d5-8de5-4c54-ae70-b6a498ab4e9e",         "auditBatchId": "e35fd529-613f-5e79-036f-f37c2801041d",         "eventId": "49dcbe2c-51a8-11ee-9348-3cecefd01508",         "eventType": "TRIP",         "eventTimeStamp": 1694549374,         "auditResult": false,         "auditCorrections": [],         "auditedTimestamp": 1694635817,         "auditedBy": "ppradeep@etcc.co

An in-depth guide into starting StreamSets, deploying engines, and running pipelines. Overall architecture recapThe control plane of StreamSets Platform, Control Hub, hosted in the cloud. The data plane encompasses StreamSets Data Collectors (SDCs), which should be installed in a customer’s network, be it in the cloud or on-premise.  Consider these options for SDC installation (not all of them are recommended for production scenario):  Tarball (binary download) Docker container Windows PC not supported   OK – the fastest to implement Linux/Mac OK with configured prerequisites  Depending on your choice, find below instructions for major steps of tarball and Docker options. Provide and prepare your machineUse your own laptop or create a VM in the cloud of your choice. VM size should be determined by the minimum requirements for SDC installation: 2 vCores, 1GB RAM, 6GB disk space.If on Linux, run a system update command, like yum updat

hello,I’m new to streamsets so it might be an obvious question!I’m using “data generator” to accept the json input and transform to XML, however I want to add few namespaces in the generated XML output. Please can anyone suggest how to achieve that?This is the output “data generator” is producing:<?xml version="1.0" encoding="UTF-8" standalone="no"?><root> <id>file</id> <value>File</value> <popup> <menuitem> <value>New</value> <onclick>CreateDoc()</onclick> </menuitem> <menuitem> <value>Open</value> <onclick>OpenDoc()</onclick> </menuitem> <menuitem> <value>Save</value> <onclick>SaveDoc()</onclick> </menuitem> </popup></root>What changes do I need to make it something like this (the element id is under “b” namespace):<?xml version="1.0" encoding="UTF-8" standalone="no" ?&g

 Running Error pipeline couldn`t stop, when I click the button of force stop, nothing happened, what should i do?

HiI'm currently working on implementing a metadata-driven pipeline. One of the key components of this pipeline is a job that's responsible for transferring data from Teradata to Snowflake. To make this process dynamic and reusable, I've introduced a job which will load the data to snowflake.Furthermore, I've established a separate pipeline that serves the purpose of fetching metadata from Teradata. This metadata contains important information, including the values for ${dbname} and ${Tname}. The intention is to pass these parameter values to the "startjobs" process. However, I'm currently unsure about how these parameter values will be effectively utilized within the job I've created for the data transfer from Teradata to Snowflake. I would greatly appreciate any guidance or assistance in this regard.  

I am trying to create a job instance from the job template. I have passed the runtime parameters to the start job component but get the following error. - Start failed for job template ID: START_JOB_14 - Start failed for job template ID: abc: com.streamsets.pipeline.lib.ControlHubApiException: Unexpected exception from Control Hub: START_JOB_05 - Failed to parse runtime parameters for job ID: abc, error: 400: I have made sure that the parameter name is correct. Please help me with why is it not able to parse the runtime parameters?  

Hello, AVG has quarantined CefSharp.BrowserSubprocess.exe as a possible IDP—generic infection. Slido doesn't function, and it's been quarantined.How should I proceed?