Skip to main content

Brinqa Connect Releases

info

To download the latest version of Brinqa Connect, please visit https://connectors.brinqa.io/#/downloads.

For Brinqa Connect documentation, please visit https://docs.brinqa.com/docs/brinqa-api/brinqa-connect-api.

Version 1.10.4​

Released June 26th, 2024

  • Fixed decoding issues with special characters in API keys.

  • Fixed the DELETE operation on API keys.

Version 1.10.3​

Released June 19th, 2024

  • Added de-duplication at the batch layer and serialized storage.

  • Fixed a caching issue in the Type Definition layer.

Version 1.10.2​

Released June 7th, 2024

  • Added an endpoint for streaming data, which provides the ability to stream large numbers of entities with minimal memory usage on the server.

  • The endpoints that accept data (/api/v(1|2)/data) now support streaming data input data. However, for larger POST requests, it is best practice to limit entries to 100-200, especially if you need to retry the request.

    warning

    The /api/v(1|2)/data reads or GET requests now have a hard limit of 10,000. Any request exceeding this limit will return an HTTP 400 error code. This constraint is designed to protect the system from potential memory exhaustion due to large requests. For large requests, consider using the new Streaming API endpoint. Refer to the Streaming API endpoint documentation for more details.

Version 1.10.1​

Released May 31, 2024

  • Added an endpoint, API Key Management, which provides the ability to add new API keys for self-management.

Version 1.10.0​

Released May 24th, 2024

  • Fixed vulnerabilities identified in Brinqa Connect 1.9.3.

  • Brinqa Connect version 1.10.0 includes a new storage engine, our fourth revision since launching Brinqa Connect. This new engine is specifically designed to handle large values efficiently. Often, objects in Brinqa Connect contain numerous values or an outsized value like a description. Large values can cause write amplification in key-value stores; our new engine addresses this concern effectively.

  • In addition to the new storage engine, we have introduced a new compression process that supports lowering both storage and write amplification. Typically, compression becomes ineffective when paired with encryption. However, our new approach using Zstandard (ZSTD) has overcome this challenge, providing efficient compression even with encrypted data.

    For additional information, please refer to the following resources:

  • We understand the importance of maintaining backward compatibility. With the new storage engine, we have ensured that backward compatibility is maintained and provided a clear path for migrating to the new engine. You can now use API support to check which engine your storage identifier is using and utilize an API endpoint to migrate your storage identifier to the latest revision. For additional information and usage instructions, please refer to the "Data Management V2" section in the UI.

Version 1.9.3​

Released April 16, 2024

  • Fixed an issue with a list of objects in the /api/v1/data/{name} endpoint.

Version 1.9.2​

Released April 11, 2024

  • Fixed some vulnerabilities identified in Brinqa Connect 1.9.1.

  • Generates an error if the return list contains a null value.

  • Corrected the start and end time returned by the /api/v1/data API endpoint.

  • Fixed an authentication issue on the /api/v1/info API endpoint.

  • Updated dependencies.

  • Documentation updates:

    • Updated the JVM requirement to Java 17 LTS release.

    • Revised the relative URL for the OpenAPI sandbox.

Version 1.9.1​

Released February 2, 2024

  • Added support for reading in descending order (already supporting ascending order).

  • Added support for JDK 17 and made it a requirement.

Version 1.8.10​

Released December 23, 2023

  • Fixed the issue where Brinqa Connect would create objects with no attributes.

  • Fixed the issue where the Brinqa Connect /api/v1/info endpoint returned an HTTP 403 error.

Version 1.8.9​​

Released December 20, 2023

  • Added validation for empty and null values.

  • Fixed some vulnerabilities identified for Brinqa Connect.

  • Updated documentation regarding Brinqa Connect credentials and the path of the OpenAPI schema file.

Version 1.8.8​​

Released September 25, 2023

  • Fixed the NullPointerException when dynamically evaluating the schema (used for Data Integration configuration).

Version 1.8.7​​

Released September 15, 2023

  • Fixed the NullPointerException that resulted from replacing a regex pattern with an empty string in field transformations.

Version 1.8.6​

Released September 11, 2023

  • Users with the EGRESS role can now sync data with Brinqa Platform 11.

  • Added support for chaining transformations.

    E.g., the following configuration transforms “a123456.abc.com” to “A123456”. It uses regex to extract the hostname first, then changes the hostname to uppercase.

    {
      "fieldTransformations": {
        "hostname": {
          "@type": "regex",
          "pattern": "(\w+)\.abc\..*\$",
          "replace": "$1"
        },
        "upperHostname": {
          "@type": "chain",
          "field": "hostname",
          "transformation": {
            "@type": "upperCase"
          }
        }
      }
    }

    Note that the chain transformation occurs on the hostname, so it must be in order.

  • Added capability to combine attributes using the Java MessageFormat.

    E.g., using the configuration at the top, a simple input containing the domain and host transforms into the enriched output at the bottom.

    Configuration:

      "fqdn": {
          "@type": "concat",
          "delimiter": ".",
          "fields": ["host", "domain"]
      },
      "upperCaseFQDN": {
          "@type": "chain",
          "field": "fqdn",
          "transformation": {
            "@type": "upperCase"
          }
      },
      "fmtExample": {
          "@type": "format",
          "fields": ["fqdn", "upperCaseFQDN"],
          "pattern": "Original fqdn {0} uppercase {1}"
      }

    Input:

    [
      {
        "attributes": {
          "domain": "abc.com",
          "host": "bob"
        }
      }
    ]

    Output:

    [
      {
        ......
        "attributes": {
          "domain": "abc.com",
          "host": "bob",
          "fqdn": "bob.abc.com",
          "upperCaseFQDN": "BOB.ABC.COM",
          "fmtExample": "Original fqdn bob.abc.com uppercase BOB.ABC.COM"
        }
      }
    ]

Version 1.8.5​

Released July 21, 2023

  • Introduced new API endpoints:
    • /api/v1/flatasync: Process JSON flat files asynchronously.
    • /api/v1/tracking: Track progress of the processing.
  • Improved processing speed of the existing /api/v1/flat endpoint.
  • Added processing time to the access log.
  • Upgraded Guava to 32.1.1-jre.
  • Upgraded SnakeYAML to 2.0 to address vulnerabilities.
  • Upgraded based framework dependencies.

Version 1.8.3​

Released June 8, 2023

  • Corrected the count when data expires or is removed.

Version 1.8.2​

Released May 15, 2023

  • Added support to convert strings to lowercase or uppercase, replace strings based on regular expression, or concatenate strings. See https://<your-brinqa-platform-url>/connect/docs for instructions.

Version 1.8.1​

Released April 12, 2023

  • Fixed an issue causing the schema to expire when it shouldn’t.

Version 1.8.0​

Released March 31, 2023

  • Fixed an issue that was showing with namespaces.

  • Fixed a broken link causing a blank screen in the UI.

  • Upgraded the dependencies of Brinqa Connect.

Version 1.7.2​

Released March 22, 2023

  • Added support for using namespaces to grant user access. See https://<your-brinqa-platform-url>/connect/docs for instructions.

Version 1.7​

Released January 30, 2023

  • Added support for a new data storage technology called RocksDB, which provides instant stats and summary information. This information is kept up to date.

  • Added a new API method to determine the summary information of a particular storage identifier.

  • Added new Python examples to the distribution.

  • Added support for multiple roles per username, e.g.: EGRESS,INGRESS.

  • Improved documentation.