January 2026 Releases

Release Date - January 30, 2026


Release Date - January 30, 2026

A GenRocket Runtime update is required for this release. Please see the following page for step-by-step instructions: 


Jar FilesNew Features
Runtime version - 3.10.0


GenRocket Jar - 3.10.0.0

Engine Jar - 3.10.0.0

Generator Jar - 3.10.0.0

Receiver Jar - 3.10.0.0

GRepositoryClient Jar - 3.10.0.0

GRepository Jar - 3.10.0.0
InPlaceMasking Jar - 3.10.0.0		The following new features were in this release:
  • In-Place Masking (IPM) - GenRocket's In-Place Masking (IPM) solution is here! The new IPM capability uses Synthetic Data Replacement (SDR) to replace sensitive data, such as Names, SSNs, or Credit Card Numbers. with synthetic values directly in the database. This eliminates the need for masked copies and protects sensitive data. IPM maintains data consistency and referential integrity, whether masking one or multiple tables. 

    A new jar, InPlaceMasking Jar, is added as  part of the GenRocket runtime for this capability.

    For basic information about IPM, see In-Place Masking (IPM) for Databases Overview. Please reach out to GenRocket Support Team to get more details on enabling and using this feature.

  • Snowflake Connection using Private Key File - Users can now connect to Snowflake using a private key file. Two new properties, private_key_file and private_key_file_pwd, are required to connect using private key file. For example:

    driver=net.snowflake.client.jdbc.SnowflakeDriver
    user=<user>
    password=
    batchCount=1000
    url=jdbc:snowflake://<host>/?warehouse=<warehouse>&role=<role>&authenticator=<authenticatorType>
    private_key_file=/home/JohnDoe/Downloads/rsa_key.p8
    private_key_file_pwd=123Test
     

  • SnowflakePartitionReceiver - This Receiver creates one or more inFile descriptions and one or more Data Files containing the generated data. It is intended for use in Scenarios run by the GenRocket Partition Engine to generate large amounts of data for Snowflake; thus, its parameters will be automatically updated by the G-Partition Engine.

  • MongoIdGen - Generates a MongoDB object ID, a special 12-byte (96-bit) default identifier that MongoDB uses for all documents in a collection. This Generator has two parameters: 
    • date - input date used to generate MongoDB id. 
    • dateFormat - format of the input date (example yyyy/mm/dd)

  • JapaneseRandomGen - Randomly generates a Japanese number within a specified range.

  • JapaneseFixedFileReceiver - This Receiver writes Domain Attribute values in a fixed format to a file with SJIS encoding. It can generate half-width & full-width spacing in a fixed file.

Enhancements
The following enhancements were in this release:
  • Restrict Organization Access by IP of Origin - User access can now be restricted by allowed IP addresses. GenRocket Admins, Super Admins, and Org Admins are not restricted. Admins can go to the My Organization page and add allowed IP addresses. Only users whose login origination matches the allowed IP addresses will be permitted to log in.

  • JapaneseRangeGen - Added a numberType parameter that can be used to select how the number is generated: Kanji, Full-Width, or Half-Width. 

  • DelimitedFileMaskReceiver - The Receiver now supports data with unclosed (opening) double quotation marks, preventing processing failures.

  • RestDirectoryV2Receiver -The Receiver can now retrieve and use authorization details provided by AWS Lambda for login.

  • AWSRoleBasedS3Receiver - The roleARN parameter, used to define the Amazon Resource Name (ARN), has been made optional within the Receiver configuration. This allows the default role to be used without explicitly specifying it within the Receiver configuration.

  • DatabricksPartitionReceiver - An executeParquetFile parameter has been added and determines if the GenRocket Receiver should connect to the database and load the generated Parquet files. If 'false', it will not connect to the target database and just generate the files.

  • OraclePartitionReceiver - A new logging parameter, sqlLoaderLogging, has been added for SQL Loader, which is a tool used to import large amounts of data from the generated files into the Oracle database. This parameter defines defines whether the log files should be generated inside a 'log' folder within the designated output folder.

  • XMLTemplateReceiver - Three new parameters have been added to this Receiver for defining optional sub-directories: outputSubDir, configSubDir, and templateSubDir. 

  • G-Repository Client - We have increased the number of retry attempts and decreased the wait time when a G-Repository Client accesses resources from the G-Repository Server.

  • Team Management APIs- The Project List API can now be filtered by team permission, displaying only the projects assigned to the team associated with the logged in user's account. Two new APIs have also been added for managing teams within an organization.
    • Get List of Teams by User - rest/team/users
    • Get List of Users by Team - rest/user/teams


  • DatabricksPartitionReceiver - The Receiver can now retrieve and use authorization details provided by AWS Lambda while connecting to Databricks database..

Bug Fixes
The following bug fixes were in this release:
  • ListRepoQueueHistory REST API - The GMUS request status was showing as 'success' even after an error was received.

  • Team Management - Adding a user to a team did not automatically grant project permissions.

  • G-Query & QueryToMapGen with Snowflake - A user received a "column not found" error when attempting to query Snowflake with the QueryToMapGen.

  • Updating Queries within a G-Query - A query was not being saved in a G-Query due to a JSQLParser exception. When attempting to save, the user received an 'Unable to Save Query' error.

  • API Method repoClientCreate - The API call to create Repo Client stopped working because of a check for queue availability.

  • GenericSQLInsertV2Receiver - A user was receiving a NullPointerException when setting the loopCount to '0' and using this Receiver to generate their data.

  •  XMLTemplateReceiver - An IndexOutOf Bounds exception was received because the line trimming performed during buffer size calculation was not included in the trimmed content.

  • FileMaskMultiBlockReceiver - The Receiver was adding an empty line in the generated file.

  • GMUS Request - An empty API block within the request resulted in a data conversion error while adding the request to GMUS queue