Sift VS partiql-lang-kotlin

Awesome! Would love to see an implementation. I worked on something similar over the Summer. It’s just relational algebra with pipes for composition. If you are interested, we could get an antlr grammar going and plug it into this basic execution engine to get a feel for the language.

- https://github.com/RCHowell/Sift

Ion is heavily used on the retail side of Amazon, but it's only recently started to appear in AWS products.

AWS is starting support PartiQL (https://partiql.org/) queries in some places and PartiQL uses Ion's type system internally.

Yep, that's exactly the vision here. One of the biggest sources of precedent and inspiration for us here is https://partiql.org/ which is picking up a fair bit of traction across AWS. Also see https://rockset.com/

QLDB allows you to create a ledger that acts similar to a schema or table space in a traditional database. Once you've created this ledger, you create a table through the SQL-like query language PartiQL that also enables you to interact with the data.

PartiQL[0] is an open source library that is a superset of SQL that I really like. It supports querying nested structures inside columns, so if a column contains some JSON data you can use the standard dot notation to query nested JSON data directly

[0] https://partiql.org/

PartiQL was introduced to AWS DynamoDB, with AWS making the announcement in 2020 making the life of developers easier, with the comfort of executing commands similar to SQL.

I haven't tried it, but I'm pretty sure the problem is that timestamp (and it's various capitalizations) is a keyword in PartiQL (https://github.com/partiql/partiql-lang-kotlin/blob/master/lang/src/org/partiql/lang/syntax/LexerConstants.kt#L221). To get it to be interpreted as an attribute name, you need to enclose TimeStamp in double quotes.