Known Limitations

This document applies to Materialize v0.17.0.

The following links describe features that Materialize does not yet support, but plans to in future releases. If any of these issues impact you, feel free to let us know on the linked-to GitHub issue.

SQL

Types

• char list is not yet supported (#7613)

Performance

• ANY and ALL queries generate suboptimal plans (#744)

Functions

• Materialize does not support window functions. In some cases, you may be able to achieve the desired results with temporal filters or the TOP K by group idiom instead. (#213)
• Table functions in scalar positions are only partially supported. We currently support no more than one table function in scalar position, which can only be situated in the query’s outermost projection. (#1546)

Common table expressions (CTEs)

• CTEs only support SELECT queries. (#4867)
• WITH RECURSIVE CTEs are not available yet. (#2516)

Joins

• The combining JOIN type must be INNER or LEFT for LATERAL references.
• Nested joins do not support LATERAL references.

COPY FROM

• CSV-formatted data does not strictly adhere to Postgres' semantics. (#9074, #9075)

Sources & sinks

Kafka

• Protobuf data for Kafka sinks is not supported (#1541)

Kinesis

• Consistent Kinesis sources are not supported (#2191)
• Enhanced fan-out Kinesis consumers are not supported (#2192)
• Reading from a Kinesis stream as of a sequence number or timestamp is not supported (#2294)
• Kinesis resharding is not supported (#8776)
• Kinesis sinks are not supported (#2372)

File sources

None right now!

Regex formatting

• Regex columns cannot be set as nullable (#1685)

Deployment

Performance

• Slow queries can impact other, unrelated queries (#1956)

Networking

• Hostnames that resolve to multiple addresses are not supported (#502)

Monitoring & debugging

• No report exists to show memory usage for indexes (#1532)

Closed known limitations

The following issued used to be known limitations, but we’ve fixed them in the specified version.