Matteo Pelati

Results 19 issues of Matteo Pelati

Sometimes pictures like 9(8) are actually not referring to integer values. For example, many mainframe files use 9(8) to represent a date. This means that the value should not be...

enhancement
question
accepted

## Description Dozer streaming SQL does not currently support the `IN` operator. We need to extend support for `IN` with the following formats: ### Lookup from a static list of...

💎 Bounty

A few days ago we published an article (https://getdozer.io/blog/llm-chatbot) describing how Dozer could improve hyper-personalization when used together with LLMs, Vector databases, and Langchain. The article describes a hypothetical bank...

documentation
💎 Bounty

## 📝 Description: This is a proposal for a new feature in Dozer Core, to enhance the functionality by allowing users to define a SQL User Defined Function (UDF) implemented...

💎 Bounty

The following query does not work ``` SELECT PULocationID, DOLocationID, window_start AS day, pu_zones.Zone as PULocationName, do_zones.Zone as DOLocationName, AVG(fare_amount) as avg_amount INTO avg_fares FROM TUMBLE(trips, tpep_pickup_datetime, '1 DAY') INNER...

bug
sql

In cases when gRPC port 50051 is already taken, Dozer boots up without reporting any error even if it cannot bind to that port. As a result, many functionalities of...

bug
live

We need to verify installation steps described here: https://getdozer.io/docs/installation are fully working on a clean machine (including pre-requisite installations). We should also automate these checks to validate the process is...

This statement: ``` SELECT PULocationID, DOLocationID, pu_zones.Zone as PULocationName, do_zones.Zone as DOLocationName, AVG(fare_amount) as avg_amount INTO avg_fares FROM TTL(TUMBLE(trips, tpep_pickup_datetime, '1 HOUR'), window_end, '1 HOUR') INNER JOIN zones pu_zones ON...

bug
sql

Currently filtering records is always executed after a product. The reason for this is because the filter condition might be applied using a function requiring inputs from multiple joined tables....

When a record needs to be updated following a JOIN, the current implementation sends a DELETE message followed by an INSERT message. This can be optimized using UPDATEs.