Changes to Configuration
To assist administrators in managing configuration, these section provides a per-release set of updates to configuration.
Platform settings appear in the Admin Settings page. From the left nav bar, select User menu > Admin console > Admin settings. See Admin Settings Page.
For more information on configuration in general, see Platform Configuration Methods.
Settings pertaining to the workspace environment and its users are available through a different page. From the left nav bar, selectUser menu > Admin console > Workspace settings. See Workspace Settings Page.
Release Updates
Release 8.11
Sample sizes can be configured to be up to 40MB in size
Beginning in this release, sample sizes can be configured to be up to 40MB in size.
Note
The Designer Cloud Powered by Trifacta platform now permits creation and storage of samples up to 40 MB in size. This size is four times the size of samples in previous releases. Details on how to change this size are below.
Changes in configuration:
New settings allow for:
setting the default and maximum size of sample displayed in browser
users can override the actual size of the sample downloaded to their browser based on their own experience
setting the maximum size of samples stored on the backend
Previous settings on configuring sample size have been deprecated.
New settings:
Setting | Default value | Description and Notes |
|---|---|---|
webapp.client.defaultLoadLimit | 10485760 | Sets the default maximum number of bytes that can be loaded into the browser for samples. This default figure remains at 10 MB. Note On a per-recipe basis, users can override this setting through the Transformer page. See Change Recipe Sample Size. |
| 41943040 | Sets the maximum number of bytes that can be loaded into the browser for samples. This limit is now set to 40 MB. Note This value cannot be overridden by users. Users can set the sample size in their browser up to this limit and no higher. |
| 41943040 | Sets the requested size of samples in bytes that are stored in the base storage layer for each sample. This limit is now set to 40 MB. Note This parameter defines the storage size of samples on the backend. Default storage size is four times larger than in previous releases. Note For datasources that must be decompressed or converted during ingest, the actual storage volume may be larger than this limit. |
Old settings:
Note
In most environments, these settings were left at their default values. They are now deprecated.
Setting | Default value | Description and Notes |
|---|---|---|
webapp.client.loadLimit | 10485760 | Defined the number of bytes that could be downloaded to the web browser, which limited the size of samples. Note Setting is now deprecated and is no longer available in the Admin Settings page. |
webapp.client.maxInternalFormatJsonBytes | 39321600 | Defined the number of JSON bytes that could be loaded into the browser from internal objects, including samples. Note Setting is now deprecated and is no longer available in the Admin Settings page. |
For more information, see Configure Application Limits.
Release 8.2
Photon running environment now enabled through Admin console
You can now enable or disable Photon execution through the Admin console.For more information, see Workspace Settings Page.
Removed settings
The features for the following settings are now a part of the core product and can no longer be disabled. These settings have been removed.
Settings | Setting Description | Notes |
|---|---|---|
Detect maximum column count in XLSX sheet | When you have enabled the Apache POI method for converting Excel files, you can enable this feature to force the conversion service to detect the maximum number of columns in an Excel sheet before beginning the conversion. | Set to true by default, so this setting was no longer needed. |
Enable Apache POI based converter for Excel data conversion | When this setting is enabled, the conversion service uses the Java-based Apache POI converter to convert Excel data for ingestion into the product. | Set to true by default, so this setting was no longer needed. |
Release 8.0
Collaboration settings apply to both flows and plans
In previous releases, the collaboration features (export, import, and sharing) for flows and plans were managed under different settings. These configuration flags to enable the following capabilities have been consolidated:
Note
When plans have been enabled, the following flags apply to both flows and plans.
Old Setting | New Setting | Doc for Flows | Doc for Plans |
|---|---|---|---|
Flow export | Export | ||
Flow import | Import | ||
Flow sharing | Sharing |
For more information on modifying these settings, see Workspace Settings Page.
Release 7.10
Ability to list users is now configurable
Beginning in this release, workspace administrators can choose whether or not individual users are able to see lists of all users in the workspace. When enabled, for example, users who are trying to share their flows can review the list of all workspace users from which they can select the users to share.
Note
Accessible information can include user email addresses. Some workspace administrators may choose to disable this feature for security reasons. Users are still able to select users if their full email addresses are known.
For more information, see Workspace Settings Page.
Release 7.8
JDBC Connection pooling disabled
Beginning in Release 7.8, JDBC connection pooling is disabled for all environments. This implementation of JDBC-based connection pools has been a source of functional and performance issues, which led to jobs failing. When JDBC connection pooling is disabled:
The connections made at the platform level are now created on an on-demand basis. For example, if you have one SQL Server Connection created through the user interface, there may be multiple JDBC connections to your SQL Server instance if multiple jobs are executing at the same time.
The ingest and publishing process may take a bit longer, since the connections are now made on-demand. Transformation jobs should not be affected, since they are executed on the running environment.
The number of physical JDBC connections should more closely match the number of jobs running concurrently.
Connection pooling may be replaced in a future release.
Note
This feature is disabled for all environments, even if it had been enabled in previous releases.
For more information, see Configure Data Service.
Release 7.6
Migrated parameters
The following parameters have been migrated from the Admin Settings page (sourced from trifacta-conf.json) into the Workspace Settings page (sourced from Configuration Service):
Old | New Configuration Service property | Description |
|---|---|---|
aws.s3.enabled | Enable S3 Connectivity | When set to Warning During upgrade, this setting may be disabled in some deployments. If your pre-upgrade environment was connected to S3, please verify that this setting is enabled in the Workspace Settings Page. See Workspace Settings Page. For more information, see S3 Access. |
For more information, see Workspace Settings Page.
Use of Spark native libraries now automatic for EMR and Databricks
Prior to Release 7.6, you could configure Spark to use Spark libraries that were either 1) on the local Trifacta node or 2) available on the cluster and provided by the Spark vendor.
Beginning in Release 7.6, Spark automatically uses the vendor libraries for EMR and Databricks clusters. If you are using a Hadoop version of Spark, you can still choose to use the local libraries.
Setting | Old value | New Value |
|---|---|---|
spark.useVendorSparkLibraries | Default is | Default is Note This value is ignored for EMR and Databricks clusters. |
For more information:
Release 7.1
Unused parameters
Setting | Changed | Setting Description | Notes |
|---|---|---|---|
feature.parameterization.maxNumberOfFilesForExecution.databricksSpark | removed | Maximum number of parameterized source files that are permitted to be executed as part of an Azure Databricks job. | Method by which parameterization is now done no longer requires a union operation between source datasets, so this setting was no longer needed. |
Migrate Data Service properties to Configuration Service
Prior to Release 7.1, a number of properties related to the Data Service have been moved from the application.properties configuration file on the Trifacta node into the Configuration Service, where these properties can be better managed across product versions and editions.
Note
These properties are not intended for customer modification. If you believe that you need to make changes to these property values, please contact Alteryx Customer Success and Services.
Old application.properties property | New Configuration Service property |
|---|---|
com.trifacta.dataservice.oracle.whitelist | dataservice.vendors.oracle.import.whitelist |
com.trifacta.dataservice.oracle.greylist | dataservice.vendors.oracle.import.greylist |
com.trifacta.dataservice.oracle.ciphers | dataservice.vendors.oracle.ciphers |
com.trifacta.dataservice.postgres.greylist | dataservice.vendors.postgres.import.greylist |
com.trifacta.dataservice.postgres.whitelist | dataservice.vendors.postgres.import.whitelist |
com.trifacta.dataservice.databricks.whitelist | dataservice.vendors.databricks.import.whitelist |
com.trifacta.dataservice.hive.whitelist | dataservice.vendors.hive.import.whitelist |
com.trifacta.dataservice.glue.whitelist | dataservice.vendors.glue.import.whitelist |
com.trifacta.dataservice.sqlserver.whitelist | dataservice.vendors.sqlserver.import.whitelist |
com.trifacta.dataservice.sqlserver.greylist | dataservice.vendors.sqlserver.import.greylist |
com.trifacta.dataservice.sqldatawarehouse.whitelist | dataservice.vendors.sqldatawarehouse.import.whitelist |
com.trifacta.dataservice.sqldatawarehouse.greylist | dataservice.vendors.sqldatawarehouse.import.greylist |
com.trifacta.dataservice.snowflake.whitelist | dataservice.vendors.snowflake.import.whitelist |
com.trifacta.dataservice.snowflake.greylist | dataservice.vendors.snowflake.import.greylist |
com.trifacta.dataservice.redshift.whitelist | dataservice.vendors.redshift.import.whitelist |
com.trifacta.dataservice.teradata.whitelist | dataservice.vendors.teradata.import.whitelist |
com.trifacta.dataservice.teradata.greylist | dataservice.vendors.teradata.import.greylist |
com.trifacta.dataservice.trifacta.postgresql.fetchSize | dataservice.vendors.postgres.import.fetchSize |
com.trifacta.dataservice.trifacta.redshift.fetchSize | dataservice.vendors.redshift.import.fetchSize |
com.trifacta.dataservice.trifacta.oracle.fetchSize | dataservice.vendors.oracle.import.fetchSize |
com.trifacta.dataservice.trifacta.sqlserver.fetchSize | dataservice.vendors.sqlserver.import.fetchSize |
com.trifacta.dataservice.trifacta.sources.databricks.enabled | dataservice.vendors.databricks.enabled |
com.trifacta.dataservice.trifacta.sources.hive.enabled | dataservice.vendors.hive.enabled |
com.trifacta.dataservice.trifacta.sources.glue.enabled | dataservice.vendors.glue.enabled |
com.trifacta.dataservice.trifacta.sources.redshift.enabled | dataservice.vendors.redshift.enabled |
com.trifacta.dataservice.trifacta.sources.postgres.enabled | dataservice.vendors.postgres.enabled |
com.trifacta.dataservice.trifacta.sources.sqlserver.enabled | dataservice.vendors.sqlserver.enabled |
com.trifacta.dataservice.trifacta.sources.teradata.enabled | dataservice.vendors.teradata.enabled |
com.trifacta.dataservice.trifacta.sources.oracle.enabled | dataservice.vendors.oracle.enabled |
com.trifacta.dataservice.trifacta.sources.bigquery.enabled | dataservice.vendors.bigquery.enabled |
com.trifacta.dataservice.trifacta.sources.sqldatawarehouse.enabled | dataservice.vendors.sqldatawarehouse.enabled |
com.trifacta.dataservice.trifacta.sources.snowflake.enabled | dataservice.vendors.snowflake.enabled |
com.trifacta.dataservice.databricks.publish.type.integer | dataservice.vendors.databricks.publish.typeMap.integer |
com.trifacta.dataservice.databricks.publish.type.string | dataservice.vendors.databricks.publish.typeMap.string |
com.trifacta.dataservice.databricks.publish.type.bool | dataservice.vendors.databricks.publish.typeMap.bool |
com.trifacta.dataservice.databricks.publish.type.float | dataservice.vendors.databricks.publish.typeMap.float |
com.trifacta.dataservice.databricks.publish.type.datetime | dataservice.vendors.databricks.publish.typeMap.datetime |
com.trifacta.dataservice.hive.publish.type.integer | dataservice.vendors.hive.publish.typeMap.integer |
com.trifacta.dataservice.hive.publish.type.string | dataservice.vendors.hive.publish.typeMap.string |
com.trifacta.dataservice.hive.publish.type.bool | dataservice.vendors.hive.publish.typeMap.bool |
com.trifacta.dataservice.hive.publish.type.float | dataservice.vendors.hive.publish.typeMap.float |
com.trifacta.dataservice.hive.publish.type.datetime | dataservice.vendors.hive.publish.typeMap.datetime |
com.trifacta.dataservice.redshift.publish.type.integer | dataservice.vendors.redshift.publish.typeMap.integer |
com.trifacta.dataservice.redshift.publish.type.string | dataservice.vendors.redshift.publish.typeMap.string |
com.trifacta.dataservice.redshift.publish.type.bool | dataservice.vendors.redshift.publish.typeMap.bool |
com.trifacta.dataservice.redshift.publish.type.float | dataservice.vendors.redshift.publish.typeMap.float |
com.trifacta.dataservice.redshift.publish.type.datetime | dataservice.vendors.redshift.publish.typeMap.datetime |
com.trifacta.dataservice.snowflake.publish.type.integer | dataservice.vendors.snowflake.publish.typeMap.integer |
com.trifacta.dataservice.snowflake.publish.type.string | dataservice.vendors.snowflake.publish.typeMap.string |
com.trifacta.dataservice.snowflake.publish.type.bool | dataservice.vendors.snowflake.publish.typeMap.bool |
com.trifacta.dataservice.snowflake.publish.type.float | dataservice.vendors.snowflake.publish.typeMap.float |
com.trifacta.dataservice.snowflake.publish.type.datetime | dataservice.vendors.snowflake.publish.typeMap.datetime |
com.trifacta.dataservice.snowflake.publish.type.time | dataservice.vendors.snowflake.publish.typeMap.time |
com.trifacta.dataservice.snowflake.publish.type.date | dataservice.vendors.snowflake.publish.typeMap.date |
com.trifacta.dataservice.sqldatawarehouse.publish.type.integer | dataservice.vendors.sqldatawarehouse.publish.typeMap.integer |
com.trifacta.dataservice.sqldatawarehouse.publish.type.string | dataservice.vendors.sqldatawarehouse.publish.typeMap.string |
com.trifacta.dataservice.sqldatawarehouse.publish.type.bool | dataservice.vendors.sqldatawarehouse.publish.typeMap.bool |
com.trifacta.dataservice.sqldatawarehouse.publish.type.float | dataservice.vendors.sqldatawarehouse.publish.typeMap.float |
com.trifacta.dataservice.sqldatawarehouse.publish.type.datetime | dataservice.vendors.sqldatawarehouse.publish.typeMap.datetime |
com.trifacta.dataservice.sqldatawarehouse.publish.type.time | dataservice.vendors.sqldatawarehouse.publish.typeMap.time |
com.trifacta.dataservice.azure.database.resource | dataservice.azure.databaseResource |
com.trifacta.dataservice.trifacta.hive.forcekint | dataservice.vendors.hive.forcekint |
com.trifacta.dataservice.trifacta.sources.snowflake.intermediateformat | dataservice.vendors.snowflake.intermediateformat |
com.trifacta.dataservice.teradata.disable_ordering | dataservice.vendors.teradata.disableOrdering |
com.trifacta.dataservice.hive.publish.disableDistributedBy | dataservice.vendors.hive.publish.disableDistributedBy |
Release 6.5
Admin Settings or | Workspace setting | Update |
|---|---|---|
n/a | Show output directory in profile view | This parameter has been hidden, as it is now enabled by default. |
n/a | Show upload directory in profile view | This parameter has been hidden, as it is now enabled by default. |
Release 6.4.1
Following parameter was moved in this release:
Admin Settings or | Workspace setting | Update |
|---|---|---|
webapp.connectivity.customSQLQuery.enabled | Enable custom SQL query | Feature is now enabled at the workspace or tier level. For more information on this feature, see Enable Custom SQL Query. |
webapp.enableTypecastOutput | Schematized output | Feature is now enabled at the workspace or tier level. For more information, see Miscellaneous Configuration. |
Release 6.4
Parameters from Release 6.0 that are no longer available in the Workspace Settings page are now enabled by default for all users.
Some new features for this release may be enabled or disabled through the Workspace Settings page.
Release 6.0
Initial release of the Workspace Settings page. See below for configuration mapping.
Configuration Mapping
The following mapping between old trifacta-conf.json settings and new Workspace settings is accurate for the current release.
Admin Settings or | Workspace setting | Update |
|---|---|---|
webapp.walkthrough.enabled | Product walkthroughs | |
webapp.session.durationInMins | Session duration | |
webapp.enableDataDownload | Sample downloads | |
webapp.enableUserPathModification | Allow the user to modify their paths | |
webapp.enableSelfServicePasswordReset | Enable self service password reset | |
webapp.connectivity.customSQLQuery.enabled | Enable custom SQL query | |
outputFormats.Parquet | Parquet output format | |
outputFormats.JSON | JSON output format | |
outputFormats.CSV | CSV output format | |
outputFormats.Avro | Avro output format | |
outputFormats.TDE | TDE output format | |
feature.scheduling.enabled | Enable Scheduling feature | |
feature.scheduling.schedulingManagementUI | Scheduling management UI (experimental) | Now hidden. |
feature.scheduling.upgradeUI | Show users a modal to upgrade to a plan with Scheduling | Now hidden. |
feature.sendFlowToOtherPeople.enabled | Allow users to send copies of flows to other users | As of Release 6.10, this feature has been removed from the product. |
feature.flowSharing.enabled | Enable Flow Sharing feature | |
feature.flowSharing.upgradeUI | Show users a modal to upgrade to a plan with Flow Sharing | Now hidden. |
feature.enableFlowExport | Allow users to export their flows | |
feature.enableFlowImport | Allow users to import flows into the platform | |
feature.hideAddPublishingActionOptions | Forbid users to add non-default publishing actions | |
feature.hideUnderlyingFileSystem | Hide underlying file system to users | |
feature.publishEnabled | Enable publishing | |
feature.rangeJoin.enabled | Enable UI for range join | |
feature.showDatasourceTabs | Show datasource tabs in the application | |
feature.showFileLocation | Show file location | |
feature.showOutputHomeDirectory | Show output directory in profile view | |
feature.showUploadDirectory | Show upload directory in profile view | |
metadata.branding | Branding to use in-product for this deployment | Now hidden. |
webapp.connectivity.enabled | Enable Connectivity feature | |
webapp.connectivity.upgradeUI | Show users a modal to upgrade to a plan with Connectivity | |
feature.apiAccessTokens.enabled | API Access Token |