Weekly Community Meeting – Wednesday, May 13 at 5 PM PDT

[Bismanpal Singh Anand <bi...@gmail.com>]

Hi everyone,

Our *weekly Apache ResilientDB (Incubating) community meeting* will be held
on *Wednesday**, May 13 at 5 PM PST* via *Zoom*. These meetings are open to
all contributors and community members interested in ongoing development,
research, and incubation progress.

*When:* Wednesday, May 13 at 5 PM PST
*Where:*
https://ucdavis.zoom.us/j/95534430002?pwd=pLKg4fgf58lI7bZ6Ai17nP4u5YRM5Z.1


*Agenda for This Week:*

   -

   Review progress on cleanup pull requests and configuration updates
   -

   Status on PPMC members' subscription to private list
   -

   Status updates on Apache Incubating ResilientDB Graduation process
   -

   Updates on persistent account storage in ResilientDB
   -

   Open floor for community updates and questions

Meeting notes will be shared on this list afterward for those who can’t
attend.
-
Best,

*Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)

Re: Weekly Community Meeting – Wednesday, May 13 at 5 PM PDT

[Bismanpal Singh Anand <bi...@gmail.com>]

Hi everyone,
Here’s a brief summary of our weekly *Apache ResilientDB (Incubating)*
community
meeting held on *May 13, 2026* for those who couldn’t attend:

*Action Items:*

   - Create an issue (if possible) or update the existing issue with
   detailed background and motivation for the secondary index feature, and
   link it to the PR.
   - Move the DuckDB build flag fix from the dev server to the master
   branch for Josh.
   - Josh: Run longer-term tests (starting with 3 nodes, 1-10 minutes
   duration) for the Raft implementation and report results.

*ResilientDB Secondary Index Implementation*
Shray submitted a pull request to implement secondary indexes in
ResilientDB, focusing on changes to the storage layer for creating and
managing composite keys. Mohammad advised Shray to subscribe to the dev
mailing list and share the contribution publicly with the community.
Junchao requested more background on the feature's purpose, which Shray
explained would enable faster lookups using composite keys rather than
filtering records client-side. The team discussed that Harish had
previously created an issue for this work but hadn't made significant
progress, and Bismanpal noted that Harish's experimental results were
likely local and not committed to any branches.

*ResilientDB Composite Keys Implementation*
The team discussed a PR related to implementing composite keys in
ResilientDB to enable more efficient filtering and data retrieval. Mohammad
explained that the current system requires fetching all data and filtering
in the application, which is inefficient, while the proposed change would
allow filtering directly in the database using secondary indexes. Junchao
requested more detailed documentation in the pull request and issue to
better understand the implementation and its benefits. Shray agreed to
create a concise design document explaining the problem and solution, and
Mohammad suggested sending it to the dev channel. Bismanpal also provided
an update on working on a persistent account issue for smart contracts,
addressing temporary storage that gets deleted upon server restart.

*Project Updates and Progress Discussion*
The team discussed updates on various projects. Josh reported progress on
implementing Raft, including adding tests and formatting cleanup, but
encountered issues with CloudLab access due to excessive SSH requests.
Mohammad advised Josh to consult with Shaokang and Dakai about
configuration settings and suggested starting with 3 nodes for testing.
Bismanpal mentioned fixing a DuckDB compilation issue that was causing
build problems. Devang shared updates on ResShare, creating a new
repository and transferring ownership to ResilientApp, with plans to
implement better security and worker queues. The team agreed to proceed
with the current release despite not having Raft in master yet, and
Mohammad encouraged Josh to contact CloudLab support about his access issue.

-
Best,

*Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)




-- 
-
Best,
Bismanpal Anand
+1 (530) 979-7760
Portfolio <https://bismanpal-anand.com/> | Linkedin
<https://www.linkedin.com/in/bismanpal-anand/>