eventsourcing/es4j

Problem: Min/Max queries are global to the attribute

Open

#209 opened on Jan 27, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (27 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (406 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

At this moment, Min/Max queries are limited to finding the smallest or largest value of a particular attribute globally across an entity. Which means you can tell "what's the latest order" but not "what's the latest order for this person". IsLatestEntity/LatestAssociatedEntryQuery are currently being used to address this type of need, but they are very slow and cumbersome. Min/Max has been already optimized for PostgreSQL storage.

It would have been great if it was possible to fit this type query within Min/Max as an option:

// Find the last order for user with id=<id>
max(Order.TIMESTAMP, equal(Order.USER_ID, id))
// Find all last orders for all users
max(Order.TIMESTAMP, Order.USER_ID)

(Or something similar)

Contributor guide

Research direction
Implement min/max queries with optional filter or group by parameters, similar to the proposed syntax.
Tech stack
java
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Javaevent sourcing basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40