Adam Retter

I think there are clearly two different things being reported in this issue: 1. The memory leak I initially reported in the Full-Text and Range indexes (implemented atop Lucene) 2....

> The first thing I will do is provide a checksum of the heap dump file I have added the exact details now at the top of this thread in...

@line-o @reinhapa Would you be able to open a new issue for the other memory leak you believe you are seeing please, and copy all details there and add anything...

> I can not reproduce the issue you describe. Yes, I was already clear on that. I am not sure why, as I and others can reproduce it. Anyway, I...

The Java code that processes: `attribute="wwp:field"` looks quite questionable: https://github.com/eXist-db/exist/blob/eXist-6.2.0/extensions/indexes/range/src/main/java/org/exist/indexing/range/RangeIndexConfigAttributeCondition.java#L70 i.e.: ```java this.attributeName = elem.getAttribute("attribute"); if (this.attributeName == null || this.attributeName.isEmpty()) { throw new DatabaseConfigurationException("Range index module: Empty or no...

I agree this is a worthy addition to be added to the core in Java. In the past almost all projects that I undertook required me to write a function...

@line-o I don't think that needs to be done.

@line-o That's one perspective... feel free to send a follow-up PR.

> I would propose to shift the current mapping of node types by one which would make the relationship quite clear as all types that are subtypes of NODE would...

> Some test fail too.. @reinhapa Yes, I added a whole load of new tests which show existing problems in eXist-db, I have just one case left to solve and...