Upgrade: Filter

Maia has a Filter component that's equivalent to the Matillion ETL Filter component, so Filter components will migrate automatically.

Maia treats the Value field of a Basic mode Filter component as a literal value, which causes an incompatibility with SQL expressions imported from a Matillion ETL Filter component. To work around this problem, see Upgrade path, below. This issue does not exist in Advanced mode filters.

The Filter components for Databricks in Matillion ETL and Maia differ in how single quotes ('), double quotes ("), and backticks (`) are handled in filter expressions. Manual intervention may be required after migration to ensure the filter expressions behave as expected. See Upgrade path for Databricks, below.

---

Upgrade path

As Matillion ETL and Maia treat expressions in Basic mode filters differently, you may need to take action to fix these items during migration.

• If your job uses only Advanced mode filters, you don't need to take any action.

• If your job includes any Basic mode filters, you should do one of the following:

  • Manually edit the Filter components after importing to Maia, to fix or recreate any filter conditions.
  • Convert the filter to Advanced mode during the import. This can be done automatically by following the procedure given below.

When you import a Filter component to Maia, the migration report will identify any potential problems and alert you that a workaround is needed. To implement the workaround:

1. Click Edit preferences in the Importing files panel.
2. Toggle Auto-convert filter components with SQL expressions to Advanced mode to On. The default setting for this option is Off, meaning that no components will be converted unless you explicitly enable it.
3. Click Apply & re-run.
4. Check the migration report to confirm that the conversion has taken place.
5. Click Import to complete the import process, and continue as described in Import to Maia.

---

Upgrade path for Databricks

When migrating Matillion ETL Filter components that target Databricks, the quoting behavior of filter expressions may differ between Matillion ETL and Maia. This is due to differences in how the two platforms handle quotes in SQL expressions.

The following table summarizes how different uses of quotes in Matillion ETL Filter components will be handled during migration to Maia. If you have filter expressions that use quotes, you should review them after migration to ensure they behave as expected.

In the following table:

• Filter value is the value set in the Matillion ETL Filter component.
• Source column type is the data type of the column being filtered.
• SQL Matillion ETL is the SQL that is generated by the Matillion ETL Filter component.
• SQL Maia is the SQL that would be generated if the filter value were used in a Maia Filter component directly.
• Value on import is the value that will be set in the Maia Filter component after migration.
• SQL Maia imported is the resulting quoting of the SQL in Maia.

Filter value	Source column type	SQL Matillion ETL	SQL Maia	Value on import	SQL Maia imported
a	string/text	'a'	'a'	a	'a'
'a'	string/text	'a'	'\'a\''	a	'a'
"a"	string/text	`a`	'"a"'	`a`	`a`
`a`	string/text	`a`	`a`	`a`	`a`
2025-11-24	datetime-like/boolean	'2025-11-24'	'2025-11-24'	2025-11-24	'2025-11-24'
'2025-11-24'	datetime-like/boolean	'2025-11-24'	'2025-11-24'	2025-11-24	'2025-11-24'
"a"	datetime-like/boolean	`a`	'"a"'	`a`	`a`
`a`	datetime-like/boolean	`a`	`a`	`a`	`a`
1	anything else	'1'	1	1	1
'1'	anything else	'1'	'1'	1	1
"a"	anything else	`a`	"a"	`a`	`a`
`a`	anything else	`a`	`a`	`a`	`a`