Shift support for "collection filtering" to Java 8 Streams

Description

Historically Hibernate allowed "filtering" a collection through a special form of Query accessible via Session#createFilter. I would like to shift this to instead leverage Java 8 streaming. There are a 2 main reasons for this:

  1. First and foremost it is a more natural idiom given Java 8's introduction of streaming APIs

  2. Secondly the Query API based filtering adds crazy requirements on the Query grammars and translators which I'd like to clean up.

follows up on

relates to

Activity

Show:

Steve Ebersole October 8, 2021 at 7:06 PM

If it comes back up, fine. But we've been punting this Jira down the road for years now

Steve Ebersole January 12, 2017 at 12:46 PM

For the moment I have this scheduled for 6.0, but that is simply to not lose track of it. This will most likely not happen for 6.0, more like some 6.x

Steve Ebersole January 12, 2017 at 12:43 PM

Regarding:

  1. http://lists.jboss.org/pipermail/hibernate-dev/2016-December/015666.html

  2. http://lists.jboss.org/pipermail/hibernate-dev/2017-January/015667.html

We agreed to dropping support for Session#createFilter in 6.0.

The next step would be filtering, etc based on Java 8 Streams in some 6.x. To be clear this is intended as an interpretation of the Stream operations into SQM/SQL query to resolve the results.

Won't Do

Details

Assignee

Reporter

Priority

Created July 17, 2016 at 2:14 PM
Updated October 8, 2021 at 7:06 PM
Resolved October 8, 2021 at 7:06 PM