Hi! There are a few things to talk about here. Let’s go through them one-by-one.
First, the free version of Nexus Repository is what we call “Community Edition.”
The 100,000 component limit you were warned about isn’t actually a limit. At around 100,000 components, your Nexus Repository will suggest you move to Postgres for stability and performance reasons. The H2 database isn’t meant to handle that many components. The Nexus Repository UI is just warning you that moving to Postgres will result in better performance, and you’ve already migrated – good job!
But there is a limit to be aware of. Community Edition permits 40,000 total components or 100,000 requests per day. If you’re over either of those limits, you get a grace period where operations continue as normal – that’s why the message says “March 23,” over a month away.
On March 23rd, if your total number of components is still above 40,000, you won’t be able to add new components. It’s a limitation of Community Edition. It has nothing to do with your database. Either remove components down to 40,000 (cleanup policies can help!) or think about purchasing a Pro license.
You’ll notice that I edited your original post to remove references to a configuration option. That option does not remove the limit. There is no configuration option for bypassing the limits imposed by Community Edition without upgrading to Pro. The limits aren’t a feature flag or configurable telemetry switch.
If you have additional questions about usage and limits, start with our documentation on the subject here.