[MGNLCE-48] Switch default bundle db to H2 Created: 24/Jun/16  Updated: 09/Feb/17  Resolved: 07/Oct/16

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 1
Labels: config, h2, jackrabbit, repository
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-4030 About page cannot detect H2 database Closed
depends upon MAGNOLIA-6421 evaluate H2 database and replacement ... Closed
depends upon MAGNOLIA-6799 Manage H2 version in magnolia-project Closed
relation
is related to MGNLCE-60 Remove "too many open files" startup ... Closed
is related to MGNLEE-465 Remove "too many open files" startup ... Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Basel 64
Story Points: 1

 Description   

There is such jackrabbit-bundle-h2-search.xml provided on the wiki, props to rgange, but eventually it gets out of sync with our sources over time (e.g. search excerpts).

Basically same as we provide those 5 currently:

  • jackrabbit-bundle-derby-search.xml
  • jackrabbit-bundle-ingres-search.xml
  • jackrabbit-bundle-mysql-search.xml
  • jackrabbit-bundle-postgres-search.xml
  • jackrabbit-memory-search.xml


 Comments   
Comment by Richard Gange [ 24/Jun/16 ]

We really should update the files. We don't use bundle anymore. All PMs are pool based now.

See https://wiki.magnolia-cms.com/display/WIKI/Jackrabbit+Repository+Configuration+File for the current options provided by JR 2.8

Comment by Mikaël Geljić [ 29/Jun/16 ]

Oh, that's pretty weird. Indeed for example derby still points to a PM under "bundle" package, but as far as I could see, all of these bundle PMs have been removed as early as JR 2.2. So, either they've been relocated somewhere I didn't find, or they have internal mappings for replacement classes (those "pool" ones).
In any case, yes we should totally refresh that. Any additional input welcome

Comment by Richard Gange [ 29/Jun/16 ]

I'm pretty sure zdenekskodik knows the answer to that mystery. I'm not sure myself. He told me once but I have since forgotten

I think we should also update the SearchIndex portion of all files. The settings minMergeDocs and maxFieldLength are now deprecated and should be removed to avoid confusion. See https://wiki.magnolia-cms.com/display/WIKI/Jackrabbit+Workspace+Configuration+File

It would be cool to update the actual names of the files to something like jackrabbit-pool-derby-search.xml so that they accurately describe the file. I'm just not sure if that would have an impact on current projects since we refer to the files by name in the magnolia properties file. Perhaps we could deprecate the bundle versions. This isn't a huge deal but I wanted to point it out.

Comment by Zdenek Skodik [ 30/Jun/16 ]

Yeah, JR provides internal mappings from bundle to pool ones, e.g. see here (since 2.2, they offer also some debug logging to prove that, both iirc).

Personally myself I'd be in favor to keep the existing sample configs up to date than introducing yet one for H2 to maintain, esp. since afaik H2 is not famous when it comes to data durability, is sensitive to misconfiguration, and according to our own load tests the performance is similar to derby. What our support statistics states on it, there are only very few (~1?) customer/s on it (some have been considering it though) and it's also not famous at http://db-engines.com/en/ranking .

Generated at Mon Feb 12 00:05:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.