Page tree

Release 9.2


Contents:

Our documentation site is moving!

For up-to-date documentation of release 9.2 of Self Managed Designer Cloud, please visit us at https://help.alteryx.com/SMC/r92/.

   

Contents:


To assist administrators in managing configuration, these section provides a per-release set of updates to configuration.


  • Settings pertaining to the workspace environment and its users are available through a different page. From the left nav bar, select User 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:

SettingDefault valueDescription and Notes
webapp.client.defaultLoadLimit10485760

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.

webapp.client.maxLoadLimit41943040

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.

webapp.sampleOutputLimit41943040

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.


SettingDefault valueDescription and Notes
webapp.client.loadLimit10485760

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.

SettingsSetting DescriptionNotes

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 SettingNew SettingDoc for FlowsDoc for Plans
Flow exportExportExport FlowExport Plan
Flow importImportImport FlowImport Plan
Flow sharingSharingShare a FlowShare a Plan


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 trifacta-conf.json property

New Configuration Service propertyDescription
aws.s3.enabledEnable S3 Connectivity

When set to enabled, base S3 connectivity is possible for the workspace.

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

SettingOld valueNew Value
spark.useVendorSparkLibrariesDefault is false.

Default is true.

NOTE: This value is ignored for EMR and Databricks clusters.

For more information:

Release 7.1

Unused parameters

SettingChangedSetting DescriptionNotes
feature.parameterization.maxNumberOfFilesForExecution.databricksSparkremoved

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 Alteryx 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 propertyNew Configuration Service property
com.trifacta.dataservice.oracle.whitelistdataservice.vendors.oracle.import.whitelist
com.trifacta.dataservice.oracle.greylistdataservice.vendors.oracle.import.greylist
com.trifacta.dataservice.oracle.ciphersdataservice.vendors.oracle.ciphers
com.trifacta.dataservice.postgres.greylistdataservice.vendors.postgres.import.greylist
com.trifacta.dataservice.postgres.whitelistdataservice.vendors.postgres.import.whitelist
com.trifacta.dataservice.databricks.whitelistdataservice.vendors.databricks.import.whitelist
com.trifacta.dataservice.hive.whitelistdataservice.vendors.hive.import.whitelist
com.trifacta.dataservice.glue.whitelistdataservice.vendors.glue.import.whitelist
com.trifacta.dataservice.sqlserver.whitelistdataservice.vendors.sqlserver.import.whitelist
com.trifacta.dataservice.sqlserver.greylistdataservice.vendors.sqlserver.import.greylist
com.trifacta.dataservice.sqldatawarehouse.whitelistdataservice.vendors.sqldatawarehouse.import.whitelist
com.trifacta.dataservice.sqldatawarehouse.greylistdataservice.vendors.sqldatawarehouse.import.greylist
com.trifacta.dataservice.snowflake.whitelistdataservice.vendors.snowflake.import.whitelist
com.trifacta.dataservice.snowflake.greylistdataservice.vendors.snowflake.import.greylist
com.trifacta.dataservice.redshift.whitelistdataservice.vendors.redshift.import.whitelist
com.trifacta.dataservice.teradata.whitelistdataservice.vendors.teradata.import.whitelist
com.trifacta.dataservice.teradata.greylistdataservice.vendors.teradata.import.greylist
com.trifacta.dataservice.trifacta.postgresql.fetchSizedataservice.vendors.postgres.import.fetchSize
com.trifacta.dataservice.trifacta.redshift.fetchSizedataservice.vendors.redshift.import.fetchSize
com.trifacta.dataservice.trifacta.oracle.fetchSizedataservice.vendors.oracle.import.fetchSize
com.trifacta.dataservice.trifacta.sqlserver.fetchSizedataservice.vendors.sqlserver.import.fetchSize
com.trifacta.dataservice.trifacta.sources.databricks.enableddataservice.vendors.databricks.enabled
com.trifacta.dataservice.trifacta.sources.hive.enableddataservice.vendors.hive.enabled
com.trifacta.dataservice.trifacta.sources.glue.enableddataservice.vendors.glue.enabled
com.trifacta.dataservice.trifacta.sources.redshift.enableddataservice.vendors.redshift.enabled
com.trifacta.dataservice.trifacta.sources.postgres.enableddataservice.vendors.postgres.enabled
com.trifacta.dataservice.trifacta.sources.sqlserver.enableddataservice.vendors.sqlserver.enabled
com.trifacta.dataservice.trifacta.sources.teradata.enableddataservice.vendors.teradata.enabled
com.trifacta.dataservice.trifacta.sources.oracle.enableddataservice.vendors.oracle.enabled
com.trifacta.dataservice.trifacta.sources.bigquery.enableddataservice.vendors.bigquery.enabled
com.trifacta.dataservice.trifacta.sources.sqldatawarehouse.enableddataservice.vendors.sqldatawarehouse.enabled
com.trifacta.dataservice.trifacta.sources.snowflake.enableddataservice.vendors.snowflake.enabled
com.trifacta.dataservice.databricks.publish.type.integerdataservice.vendors.databricks.publish.typeMap.integer
com.trifacta.dataservice.databricks.publish.type.stringdataservice.vendors.databricks.publish.typeMap.string
com.trifacta.dataservice.databricks.publish.type.booldataservice.vendors.databricks.publish.typeMap.bool
com.trifacta.dataservice.databricks.publish.type.floatdataservice.vendors.databricks.publish.typeMap.float
com.trifacta.dataservice.databricks.publish.type.datetimedataservice.vendors.databricks.publish.typeMap.datetime
com.trifacta.dataservice.hive.publish.type.integerdataservice.vendors.hive.publish.typeMap.integer
com.trifacta.dataservice.hive.publish.type.stringdataservice.vendors.hive.publish.typeMap.string
com.trifacta.dataservice.hive.publish.type.booldataservice.vendors.hive.publish.typeMap.bool
com.trifacta.dataservice.hive.publish.type.floatdataservice.vendors.hive.publish.typeMap.float
com.trifacta.dataservice.hive.publish.type.datetimedataservice.vendors.hive.publish.typeMap.datetime
com.trifacta.dataservice.redshift.publish.type.integerdataservice.vendors.redshift.publish.typeMap.integer
com.trifacta.dataservice.redshift.publish.type.stringdataservice.vendors.redshift.publish.typeMap.string
com.trifacta.dataservice.redshift.publish.type.booldataservice.vendors.redshift.publish.typeMap.bool
com.trifacta.dataservice.redshift.publish.type.floatdataservice.vendors.redshift.publish.typeMap.float
com.trifacta.dataservice.redshift.publish.type.datetimedataservice.vendors.redshift.publish.typeMap.datetime
com.trifacta.dataservice.snowflake.publish.type.integerdataservice.vendors.snowflake.publish.typeMap.integer
com.trifacta.dataservice.snowflake.publish.type.stringdataservice.vendors.snowflake.publish.typeMap.string
com.trifacta.dataservice.snowflake.publish.type.booldataservice.vendors.snowflake.publish.typeMap.bool
com.trifacta.dataservice.snowflake.publish.type.floatdataservice.vendors.snowflake.publish.typeMap.float
com.trifacta.dataservice.snowflake.publish.type.datetimedataservice.vendors.snowflake.publish.typeMap.datetime
com.trifacta.dataservice.snowflake.publish.type.timedataservice.vendors.snowflake.publish.typeMap.time
com.trifacta.dataservice.snowflake.publish.type.datedataservice.vendors.snowflake.publish.typeMap.date
com.trifacta.dataservice.sqldatawarehouse.publish.type.integerdataservice.vendors.sqldatawarehouse.publish.typeMap.integer
com.trifacta.dataservice.sqldatawarehouse.publish.type.stringdataservice.vendors.sqldatawarehouse.publish.typeMap.string
com.trifacta.dataservice.sqldatawarehouse.publish.type.booldataservice.vendors.sqldatawarehouse.publish.typeMap.bool
com.trifacta.dataservice.sqldatawarehouse.publish.type.floatdataservice.vendors.sqldatawarehouse.publish.typeMap.float
com.trifacta.dataservice.sqldatawarehouse.publish.type.datetimedataservice.vendors.sqldatawarehouse.publish.typeMap.datetime
com.trifacta.dataservice.sqldatawarehouse.publish.type.timedataservice.vendors.sqldatawarehouse.publish.typeMap.time
com.trifacta.dataservice.azure.database.resourcedataservice.azure.databaseResource
com.trifacta.dataservice.trifacta.hive.forcekintdataservice.vendors.hive.forcekint
com.trifacta.dataservice.trifacta.sources.snowflake.intermediateformatdataservice.vendors.snowflake.intermediateformat
com.trifacta.dataservice.teradata.disable_orderingdataservice.vendors.teradata.disableOrdering
com.trifacta.dataservice.hive.publish.disableDistributedBydataservice.vendors.hive.publish.disableDistributedBy

Release 6.5

Admin Settings or trifacta-conf.json setting

Workspace settingUpdate
n/aShow output directory in profile viewThis parameter has been hidden, as it is now enabled by default.
n/aShow upload directory in profile viewThis 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 trifacta-conf.json setting

Workspace settingUpdate
webapp.connectivity.customSQLQuery.enabledEnable custom SQL queryFeature is now enabled at the workspace or tier level. For more information on this feature, see Enable Custom SQL Query.
webapp.enableTypecastOutputSchematized outputFeature 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.

See 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 trifacta-conf.json setting

Workspace settingUpdate
webapp.walkthrough.enabledProduct walkthroughs
webapp.session.durationInMinsSession duration
webapp.enableDataDownloadSample downloads
webapp.enableUserPathModificationAllow the user to modify their paths
webapp.enableSelfServicePasswordResetEnable self service password reset
webapp.connectivity.customSQLQuery.enabledEnable custom SQL query
outputFormats.ParquetParquet output format
outputFormats.JSONJSON output format
outputFormats.CSVCSV output format
outputFormats.AvroAvro output format
outputFormats.TDETDE output format
feature.scheduling.enabledEnable Scheduling feature
feature.scheduling.schedulingManagementUIScheduling management UI (experimental)Now hidden.
feature.scheduling.upgradeUIShow users a modal to upgrade to a plan with SchedulingNow hidden.
feature.sendFlowToOtherPeople.enabledAllow users to send copies of flows to other usersAs of Release 6.10, this feature has been removed from the product.
feature.flowSharing.enabledEnable Flow Sharing feature
feature.flowSharing.upgradeUIShow users a modal to upgrade to a plan with Flow SharingNow hidden.
feature.enableFlowExportAllow users to export their flows
feature.enableFlowImportAllow users to import flows into the platform
feature.hideAddPublishingActionOptionsForbid users to add non-default publishing actions
feature.hideUnderlyingFileSystemHide underlying file system to users
feature.publishEnabledEnable publishing
feature.rangeJoin.enabledEnable UI for range join
feature.showDatasourceTabsShow datasource tabs in the application
feature.showFileLocationShow file location
feature.showOutputHomeDirectoryShow output directory in profile view
feature.showUploadDirectoryShow upload directory in profile view
metadata.brandingBranding to use in-product for this deploymentNow hidden.
webapp.connectivity.enabledEnable Connectivity feature
webapp.connectivity.upgradeUIShow users a modal to upgrade to a plan with Connectivity
feature.apiAccessTokens.enabledAPI Access Token



This page has no comments.