dsl | small library for creating Domain Specific Languages

I have three tables: event, speaker, event_speaker

Events and speakers have an n:m relationship managed by the "event_speaker" table. I used the jOOQ maven codegen to generate files like "EventRecord" and "SpeakerRecord".

In my application I want to get all speakers for a particular event. So I need to join the "speaker" table with the "event_speaker" table to be able to limit the results by the event id:

Some Background (feel free to skip):

I'm very new to Rust, I come from a Haskell background (just in case that gives you an idea of any misconceptions I might have).

I am trying to write a program which, given a bunch of inputs from a database, can create customisable reports. To do this I wanted to create a Field datatype which is composable in a sort of DSL style. In Haskell my intuition would be to make Field an instance of Functor and Applicative so that writing things like this would be possible:

I am trying to implement paging using Paging Library 3. However, I cannot run my project after doing all the necessary steps (paging source, flow, and etc). This is the list of my dependencies:

I want to use the elasticsearch Geo-polygon query (https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-geo-polygon-query.html) or Geo-shape query inside an ingest pipeline and I've been thinking how to do it - as there is no such processor as query processor and the example for the geo polygon is with this type of query.

The reason for me trying to use this tool is to enrich documents which's country location is null, by checking their lat and lon fields and determining which country the doc is from.

Is there anyway this could be done in an ingest pipeline? Or any other way to determine a position by lat and lon within geo shapes in a pipeline?

I am a little bit confused about my network setup at home.

This is the setup:

VLAN1 - 172.16.20.0/24 VLAN2 - 10.11.12.0/24

I am in the VLAN2 net (which is my WiFi), for the moment I allowed all traffic between both subnets.

My setup uses a KVM host for most of the services, my firewall lies on this machine and is virtualized (opnsense).

So the KVM network interfaces looks like this:

I have data class

According to Official 7.x document Link

While a field is deemed non-existent if the JSON value is null or [], these values will indicate the field does exist:

Empty strings, such as "" or "-" Arrays containing null and another value, such as [null, "foo"] A custom null-value, defined in field mapping

However, My es not consider "" as not existed. Here is my Data:

Can the DefaultRecordMapper handle lists?

Model example (really getter/setter are used):

I was reading a few articles and documents over query context and filter context and learned that it is always best to use filter context if you do not need to do a full text search or scoring does not matter. In my case, I am wanting to return the logs that contain an ID... so I then realized I should just use a filter context instead of a query context. Besides the full text search or scoring is there a hard base line that defines when you should use one over the other?

So I went from my original DSL query search cmd: