Activity
From 05/16/2026 to 06/14/2026
06/12/2026
- 09:03 AM Feature #6720: lazy hydration
- Alexandru Lungu wrote:
> Well, if you have a result-set and do 3 next operations, the first two rows are lost. If yo... - 08:31 AM Feature #6720: lazy hydration
- Again, let's back up here and understand what is the case for 4GL code to access to a specific row's results after it...
- 08:07 AM Feature #6720: lazy hydration
- > This would be outside of the PRESELECT. If the buffers used for a PRESELECT query can't be accessed outside of thei...
- 07:50 AM Feature #6720: lazy hydration
- > If a FIND is executed and the FFC is used, then the id provided. The id is checked against the session cache. The s...
- 07:43 AM Feature #6720: lazy hydration
- Alexandru Lungu wrote:
> The fundamental difference between trunk and #6720 is that the session cached DMOs may get ... - 07:30 AM Feature #6720: lazy hydration
- > I'm not sure I agree on the PRESELECT. I'd like to know what the real cases are where we have to load the DMO after...
- 06:24 AM Feature #6720: lazy hydration
- Greg Shah wrote:
> Is the current implementation handling things like @OPEN QUERY@/@GET@, all scenarios that use thi... - 06:21 AM Feature #6720: lazy hydration
- I'm not sure I agree on the @PRESELECT@. I'd like to know what the real cases are where we have to load the DMO afte...
- 05:45 AM Feature #6720: lazy hydration
- > We should expand this much further as a first step. After that, we can look at optimizations to minimize cases wher...
- 04:07 AM Feature #6720: lazy hydration
- Greg Shah wrote:
> > Until now, the lazy hydration is done just for three things:
>
> We should expand this much ... - 08:40 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I changed the config to be read from directory, each database will have it's config under @database/db_name/orm/bloom...
- 06:41 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- When a record is added, we hash its indexed fields and set the corresponding bits to 1. Those bits may already be sha...
- 06:22 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I'm surprised that the solution doesn't just clear the bits associated with the deleted record.
- 06:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Greg Shah wrote:
> So there will be a "buildup" of invalid (out of date) bits for deleted records?
Yes, but a spa... - 06:13 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- So there will be a "buildup" of invalid (out of date) bits for deleted records? That is even more of a reason to re-...
- 02:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- A bloom filter is not meant to register a deleted record, there is a separate structure called counting bloom filter ...
06/11/2026
- 03:43 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Artur, a more technical question:
The Bloom data structure is inherently additive, you set/add bits as the hashes ar... - 10:37 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- The implementation is at a point where a customer project could be tested fully, I will get on with that and deffer f...
- 09:24 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Constantin Asofiei wrote:
> Artur, some questions:
> * for a running FWD server, when does this gets persisted on d... - 09:09 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Greg Shah wrote:
> I like the non-persisted nature of the design in #11526-27.
I like it too, unless the population... - 08:40 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I like the non-persisted nature of the design in #11526-27.
I don't think we can apply changes to the filter befor... - 08:37 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Artur, some questions:
* for a running FWD server, when does this gets persisted on disk? Can it recover in case th... - 08:32 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- > This is a level of speed that means we don't need to persist things in between server restarts. We could just build...
- 08:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- For now, make the location of the cache configurable. Production deployments must carefully place and secure all fil...
- 08:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- As far as memory consumption for the same 10 tables with 7mil rows goes, these are the values
if all where in the sm... - 07:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Greg Shah wrote:
> This is a level of speed that means we don't need to persist things in between server restarts. ... - 07:53 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- This is a level of speed that means we don't need to persist things in between server restarts. We could just build ...
- 07:48 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I tested the filter population on a customer db, I used 10 tables with 7.2 mil rows in total, the filters took only 1...
- 07:34 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- When it comes to security, the filters have no readable data, it is hashed and highly compressed. The more concerning...
- 07:29 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- The easiest and most performant way is to store the artifacts (serialized filters) on the server filesystem, for dist...
- 07:23 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- My point is that this should be a general solution not something hard coded to multi-tenant.
Yes, you can read the... - 07:03 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Greg Shah wrote:
> I don't understand why this would be associated with tenant data. This is a general solution for... - 06:45 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I don't understand why this would be associated with tenant data. This is a general solution for persistence, right?...
- 06:36 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I actually intended to use an external file. Adding tenant API for filter management is the better and more elegant s...
- 06:28 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Artur Școlnic wrote:
> I just realized that tenant API needs a running server, I think as a first option, manually w... - 05:49 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I just realized that tenant API needs a running server, I think as a first option, manually writing all the database ...
- 05:34 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I need a way to specify what tables need to use the filters and what config to apply to them, since filter population...
- 07:48 AM Bug #11502: Recycle dirty share H2 session
- There is a list of @c3p0@ parameters which should not be copied from primary database, like @minPoolSize@, @initialPo...
06/10/2026
- 06:31 PM Bug #11529: Incorrect Data Structure for TenantManager
- This is an issue I am thinking for some time now. It is not critical, but only because the single client using a MT-e...
- 06:02 PM Bug #11529 (New): Incorrect Data Structure for TenantManager
- 10:03 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Added artifact persistence, initialization from db, support for an Ant task. The code needs proper formatting and jav...
- 08:18 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I am planning to execute the filters initialization as Ant task, it would need to be executed after the import, stric...
- 03:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- The structure is a bit array, a very large one, 5 million for example. On write the indexed fields are hashed a few t...
- 08:33 AM Feature #6720: lazy hydration
- Greg Shah wrote:
> > Until now, the lazy hydration is done just for three things:
>
> We should expand this much ... - 06:44 AM Feature #6720: lazy hydration
- > Until now, the lazy hydration is done just for three things:
We should expand this much further as a first step.... - 05:40 AM Feature #6720: lazy hydration
- I have started to partially implement *Runtime feedback per call-site*, with the key set to @(database, fql)@.
{{C... - 03:04 AM Feature #6720: lazy hydration
- Greg Shah wrote:
> I wonder if we have minimized the hydration needed? My understanding is that previous attempts a... - 01:58 AM Feature #6720: lazy hydration
- Greg Shah wrote:
> > I have made these measurements because I need to know if fixing the performance findings, but I... - 01:12 AM Feature #6720: lazy hydration
- Ovidiu Maxiniuc wrote:
> Teodor,
> I had a quick look at the patch you posted in #6720-159. What I immediately not... - 07:14 AM Bug #11288: Check if c3p0 is required for in-memory databases
- 11288d was ported to 10614_main rev 16417.
- 06:53 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Artur, please patch 10614_main with 11288a now.
06/09/2026
- 06:47 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Sorry to play the devil's advocate.
I understand that the data structure is some kind of SQL index, mapping from ... - 10:09 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Alexandru Lungu wrote:
> This is a red flag for me. We are talking about tens of millions of record. This may requir... - 09:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- > on initialization all records are read from the db,
This is a red flag for me. We are talking about tens of mill... - 09:36 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Ovidiu, the new approach is much simpler than that. The initialized filters hold only bits, some of them are set base...
- 09:29 AM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters
- This is definitely a new approach.
Some notes in this regard:
* at 'in-memory' level, we already have @UniqueTrac... - 09:19 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Committed the initial version, so far it supports only in memory insertion/filter population and lookup, the filters ...
- 04:15 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- A Bloom filter is a space-efficient probabilistic data structure used to quickly test whether an item has been seen b...
- 04:05 AM Feature #11526 (Internal Test): Implement in-memory uniquness validation using Bloom filters
- 10:49 AM Feature #6720: lazy hydration
- > I have made these measurements because I need to know if fixing the performance findings, but I think I shall find ...
- 10:43 AM Feature #6720: lazy hydration
- Teodor,
I had a quick look at the patch you posted in #6720-159. What I immediately noticed is that it rolls back R... - 08:41 AM Feature #6720: lazy hydration
- I have done some tests *6720b* vs *trunk* and these are the measurements:
|_. scenario |_. rows |_. fields |_. 4GL (... - 03:20 AM Feature #6720: lazy hydration
- This is the list of findings for a patch which I am using (based on *6720b*):
{{Collapse(Findings)
h1. Code Review ... - 03:34 AM Bug #11502: Recycle dirty share H2 session
- It is good, but the used config for the data sources is the default one, it needs to use the tenant specific one to a...
- 03:30 AM Bug #11502: Recycle dirty share H2 session
- Can you take into the patch? Is a reasonable change?
- 03:29 AM Bug #11502: Recycle dirty share H2 session
- If it helps a customer application, I am ok with adding it back, just make sure to inherit the configuration of the d...
- 03:25 AM Bug #11502: Recycle dirty share H2 session
- Artur Școlnic wrote:
> Connection pooling was removed for the Meta and Dirty databases to simplify configuration and... - 03:07 AM Bug #11502: Recycle dirty share H2 session
- Connection pooling was removed for the Meta and Dirty databases to simplify configuration and improve maintainability...
06/08/2026
- 06:06 AM Bug #11502: Recycle dirty share H2 session
- Artur, can you explain your changes for #11288 regarding dirty database?
I think the easiest way to fix the perfor...
06/03/2026
- 04:29 AM Bug #9194 (WIP): FWD selects the wrong index when using CONTAINS?
- False alarm, it seems that the selected index is wrong even with the recent trunk. The discussion happened in #11448.
- 04:03 AM Bug #9194 (Test): FWD selects the wrong index when using CONTAINS?
05/29/2026
- 08:11 AM Bug #11502: Recycle dirty share H2 session
- Teodor, mind the effort in #8388 of dropping dirty-share being stored in H2, but in persistence database.
- 08:00 AM Bug #11502: Recycle dirty share H2 session
- Currently, on @DefaultDirtyShareManager@, when we need the dirty-share session, we use @new Session(dirtyDatabase)@ a...
- 07:43 AM Bug #11502 (Internal Test): Recycle dirty share H2 session
- 06:15 AM Feature #9545: confirm/add table parameter support
- Rebased to trunk rev. 16588.
- 06:06 AM Bug #11501: Investigate useSnapshot usage in multi-table indexed-reposition queries
- This task is dedicated for investigating how the @useSnapshot@ array shall be used in the context of an invalidate mu...
- 06:00 AM Bug #11501 (New): Investigate useSnapshot usage in multi-table indexed-reposition queries
- 05:52 AM Bug #10962 (WIP): Optimized multi-table compound components are not invalidated
- > [MAJOR] functional CompoundQuery.stateChanged: Replaces cursor.peekLastLoadedResult() with cursor.peekLastLoadedRes...
- 03:22 AM Bug #11499: Debug and fix query logging issues
- Great, thanks Alexandru.
Radu,
I am hoping you could help me with a few things, my first question is why the report... - 03:19 AM Bug #11499: Debug and fix query logging issues
- I added Radu to this task; he is the dinosaur that built this a long time ago already :)
- 02:23 AM Feature #4369 (Test): implement stateless FWD server clustering
- 4369a was merged to trunk rev. 16588 and archived.
- 01:58 AM Feature #4369 (Merge Pending): implement stateless FWD server clustering
- Eduard: please merge 4369a now.
- 01:57 AM Feature #4369: implement stateless FWD server clustering
- Ovidiu Maxiniuc wrote:
> Greg Shah wrote:
> > [...] we are waiting on Ovidiu's thoughts on the metadata configurati...
05/28/2026
- 02:11 PM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Is the wiki complete? Ovidiu, can you take a look, too? [[p2j:Stateless_Server_Clusteri... - 02:03 PM Feature #4369: implement stateless FWD server clustering
- Ovidiu Maxiniuc wrote:
> * then there is the @useMeta@ in @DatabaseManager@. Even if the meta tables are availab... - 12:50 PM Feature #4369: implement stateless FWD server clustering
- Greg Shah wrote:
> [...] we are waiting on Ovidiu's thoughts on the metadata configuration.
Yes, I am a bit concern... - 12:16 PM Feature #4369: implement stateless FWD server clustering
- Is the wiki complete? Ovidiu, can you take a look, too? [[p2j:Stateless_Server_Clustering]]
- 11:58 AM Feature #4369: implement stateless FWD server clustering
- Eduard Soltan wrote:
> Waiting for large gui application smoke tests, and I will retest chui just in case.
Large ... - 08:40 AM Feature #4369: implement stateless FWD server clustering
- Greg Shah wrote:
> Did you change the default setting for metadata (at least in non-clustered mode)?
>
Yes, now i... - 08:38 AM Feature #4369: implement stateless FWD server clustering
- Did you change the default setting for metadata (at least in non-clustered mode)?
We need clear documentation on h... - 08:32 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> OK, anything else left to test or work?
Waiting for large gui application smoke tes... - 08:09 AM Feature #4369: implement stateless FWD server clustering
- Eduard Soltan wrote:
> Constantin Asofiei wrote:
> > Did you do a security scanning of the other jars brought by ge... - 07:15 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Did you do a security scanning of the other jars brought by geode in 4369a?
Yes, ther... - 05:03 AM Feature #4369: implement stateless FWD server clustering
- Did you do a security scanning of the other jars brought by geode in 4369a?
- 04:32 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Eduard, is this gradle change in the branch? What about the other jars?
I upgraded th... - 04:27 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Eduard, is this gradle change in the branch? What about the other jars?
I committed o... - 04:21 AM Feature #4369: implement stateless FWD server clustering
- Eduard, is this gradle change in the branch? What about the other jars?
Can we finish testing today for the other ... - 11:48 AM Bug #11499: Debug and fix query logging issues
- Artur Școlnic wrote:
> Another issues is meta table logging that is logged at the persistent table level, it must me... - 07:01 AM Bug #11499: Debug and fix query logging issues
- A few explanations for the unexpected logs:
1. Some of the queries were not logged because the reported time was bel... - 06:21 AM Bug #11499: Debug and fix query logging issues
- Another feature I want to add is a base latency log, I think executing a simple @Select 1@ and logging the time is a ...
- 06:12 AM Bug #11499 (WIP): Debug and fix query logging issues
- 06:11 AM Bug #11499: Debug and fix query logging issues
- Query logging seems to have a few unexpected issues, this is one example...
- 06:03 AM Bug #11499 (WIP): Debug and fix query logging issues
05/27/2026
- 11:08 AM Feature #4369: implement stateless FWD server clustering
- ...
- 09:41 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
>
> We need to move to 6.2.18 version in build.gradle - is this possible?
>
I looke... - 05:58 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Additional testing: in multi-tenant mode and with i.e. 150 or 200 classic agents started... - 05:51 AM Feature #4369: implement stateless FWD server clustering
- Eduard Soltan wrote:
> I have tested ETF and chui on my side, they both pass.
Great, then I won't bother with ETF.
... - 05:50 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> 4369a is OK. ChUI passed, I'll let you know about ETF.
>
I have tested ETF and ch... - 05:49 AM Feature #4369: implement stateless FWD server clustering
- 4369a is OK. ChUI passed, I'll let you know about ETF.
Eduard: we need to figure out the spring library version we... - 08:39 AM Bug #7667 (Test): Support OUTER-JOIN with PRESELECT at conversion
- #11470 was fixed and support is now in trunk.
05/26/2026
- 03:53 PM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> * @GuiWebSocket.java@ needs to be reverted to trunk revision
Meant to solve some ja... - 02:38 PM Feature #4369: implement stateless FWD server clustering
- Also: please rebase when convenient so other projects can be tested.
- 02:36 PM Feature #4369: implement stateless FWD server clustering
- Eduard, good work, there are only a few more issues; I'll run ETF and ChUI with this. Please also rebase. Bellow is ...
- 01:16 PM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Eduard Soltan wrote:
> > Committed on 4369a, rev. 16616.
> >
> > I think this handle... - 12:31 PM Feature #4369: implement stateless FWD server clustering
- Eduard Soltan wrote:
> Committed on 4369a, rev. 16616.
>
> I think this handles everything.
Did you address the ... - 11:32 AM Feature #4369: implement stateless FWD server clustering
- Committed on 4369a, rev. 16616.
I think this handles everything.
About the spring-dependecy:... - 03:30 AM Feature #4369: implement stateless FWD server clustering
- Eduard, this is review for 4369a rev 16611:
* for the management of temp group and users
** there should be a singl... - 02:37 AM Feature #4369: implement stateless FWD server clustering
- Eduard, how's the testing going for other apps?
> Fix is to exclude spring-jcl dependency.
I don't see this in b... - 08:11 PM Feature #4369: implement stateless FWD server clustering
- +Review of 4369a / r16611 (with focus on persistence)+
This is a huge changeset. I focused on persistence mainly, ...
05/25/2026
- 04:43 AM Bug #7667 (Pending): Support OUTER-JOIN with PRESELECT at conversion
- This is being implemented in #11470.
- 02:16 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> > -chui regression testing (had to eliminate spring-beans-5.3.20.jar, spring-core-5.3.20... - 01:51 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Eric,
I don't expect performance in a customer application to be affected in a measurable way, this change was more ...
05/22/2026
- 12:55 PM Bug #11288: Check if c3p0 is required for in-memory databases
- What practical performance testing can we do with and without this update?
- 06:12 AM Bug #11288 (Test): Check if c3p0 is required for in-memory databases
- 11288d was merged to trunk/16577.
- 06:03 AM Bug #11288 (Merge Pending): Check if c3p0 is required for in-memory databases
- Please merge -10827b- 11288d now.
- 05:56 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Thank you, Razvan.
Constantin, please put 11288d in the merge queue when you can.
- 04:32 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Smoke-testing 11288d on a customer app passed.
- 09:11 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> > - etf (on spring project that connects to the server had to change to p2j, because I h... - 09:04 AM Feature #4369: implement stateless FWD server clustering
- Eduard Soltan wrote:
> I regression tested the changes on:
>
> -chui regression testing (had to eliminate spring-... - 08:54 AM Feature #4369: implement stateless FWD server clustering
- I regression tested the changes on:
-chui regression testing (had to eliminate spring-beans-5.3.20.jar, spring-cor...
05/20/2026
- 11:51 AM Feature #11481: Create a tool for extracting the 4GL/SQL name mapping
- > Yes, we need a tool which gets the .p2o files and emits a file for each schema and dialect. This tool can then look...
- 11:06 AM Feature #11481: Create a tool for extracting the 4GL/SQL name mapping
- Ovidiu Maxiniuc wrote:
> ** alternatively, we can write a tool for extracting this information later, from existing ... - 10:58 AM Feature #11481: Create a tool for extracting the 4GL/SQL name mapping
- Currently the [[p2j:Conversion Handbook]] and [[p2j:Conversion Reference]] describe how the identifiers for databases...
- 10:20 AM Feature #11481 (New): Create a tool for extracting the 4GL/SQL name mapping
- 09:39 AM Bug #10962: Optimized multi-table compound components are not invalidated
- To simplify the process, I plugged in the 10962a branch through an AI reviewer. I am assessing this now ATM.
* *[M... - 07:45 AM Feature #4369: implement stateless FWD server clustering
- Constantin Asofiei wrote:
> Eduard Soltan wrote:
> > Committed on 4369a, rev. 16608. Multiple code fixup, that appe... - 07:19 AM Feature #4369: implement stateless FWD server clustering
- Eduard Soltan wrote:
> Committed on 4369a, rev. 16608. Multiple code fixup, that appeared during application debug.
... - 06:40 AM Bug #11288 (Internal Test): Check if c3p0 is required for in-memory databases
- +Review of 11288d, r16571+
I see no problems in code logic. The following are just small issues to be addresses be... - 05:26 AM Bug #11288 (Review): Check if c3p0 is required for in-memory databases
- I committed the changes from the a and b branch to 11288d. Tested two customer projects, saw no regressions.
Ovidiu,... - 02:30 AM Bug #11288: Check if c3p0 is required for in-memory databases
- To further prove that the blobs are connection bound, I set @setMaxConnectionAge@ to 1 second (close connection after...
05/19/2026
- 02:04 PM Feature #4369: implement stateless FWD server clustering
- Committed on 4369a, rev. 16608. Multiple code fixup, that appeared during application debug.
- 10:15 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Artur Școlnic wrote:
> @setBytes@ solves the @JdbcSQLNonTransientException@, but not the record not being found, I n... - 09:47 AM Bug #11288: Check if c3p0 is required for in-memory databases
- The test case from #11288-40 is also failing with trunk, the find fails, I think the record is not persisted properly...
- 06:06 AM Bug #11288: Check if c3p0 is required for in-memory databases
- The test case without connection pooling is:...
05/18/2026
- 03:52 AM Feature #4369: implement stateless FWD server clustering
- Rebased to trunk 16570.
- 03:31 AM Feature #4369: implement stateless FWD server clustering
- Eduard, please rebase 4369a.
- 02:16 AM Feature #4369 (Review): implement stateless FWD server clustering
- Committed on *4369a, rev. 16552.*
Support for Redis directory and lockManager backend (for directory/database). *P...
Also available in: Atom