admin web application: indexes: contents of arbitrary files listed

[vogelsgesang]

I just added some files with names like a.a, coll.xc, ... in /db/system/config/db/test/. I was expecting that only the collection.xconf file has any influence on the configuration.

But it seems as if every file (indepedent of its name) is used for index configuration or at least displayed in the admin panel under "indexes". This results in the attached screenshot

There are 6 different, contradictory entries for the collection /db/test.

eXist version 2.2RC1

[dizzzz]

Please ask your questions on the eXist-open mailinglist instead ; http://exist-db.org/exist/apps/doc/getting-help.xml

This way the community can learn about your questions.

In general: is your ticket a question, or a remark, or a bug report?

[shabanovd]

this is clear. It's bug report.

[dizzzz]

@shabanovd it is only a bug when there use a conflict with a spec or documentation. Since no reference was specified which clears the "I was expecting" phrase, imo it is not a bug upfront. Whywas the "I was expecting" written? I have many expectations myself :-)

[dizzzz]

But ok, http://exist-db.org/exist/apps/doc/indexing.xml#idxconf has two paragraphs: 1st is only about 'an xml document', the second one refers to .xconf naming template.

eXist-db has no "create index" command. Instead, indexes are configured in collection-specific configuration files. These files are stored as standard XML documents in the system collection: /db/system/config, which can be accessed like any other document (e.g. using the Admin interface or Java Client). In addition to defining settings for indexing collections, the configuration document specifies collection-specific other settings such as triggers or default permissions.

and

Due to backward compatibility concerns, the file does not have to be called collection.xconf, which is now the preferred file name, but it must have the .xconf extension.
You can only have one.xconf file at each leve

[shabanovd]

I'd say this is UI bug

[adamretter]

I concur, it looks to me like a bug too!

If only .xconf files are meant to be used for indexes, then much more is being shown than should be (i.e. files which are not .xconf).

Also if you can only have one .xconf file - but there are two present - how do you know which eXist is using for it's index configuration?

[dizzzz]

it is just a UI thingy, like @shabanovd said; this is the code

let $xconfs := 
        for $xconf in collection('/db/system/config/')/cc:collection[cc:index]
        order by util:collection-name($xconf) 
        return $xconf

Let's not focus too much on this, @wolfgangmm has created a new XAR file based on code of @joewiz ; this functionality will disappear soonish;

about which .xconf file is used? myself I do not know, but it is actually defined.

[shabanovd]

let's keep bug open till it actually fix by something that public available, ok?

BTW, I think much better to ask index controller for such information. It'll make much less confusions.

[dizzzz]

@shabanovd probably a better idea, but there is no xquery api available for it, right?

[shabanovd]

right, this is TODO

[vogelsgesang]

@dizzzz: Sorry for including the "I was expecting" phrase. I was not completely sure if this is a bug or if there is an actual reason for displaying multiple different configurations in the UI. Hence, I referred to my expectations.

So far I am not used to your community rules. Do you want me to send this type of postings on the mailing list first? Or should I open tickets here on github when I consider something to be a bug?

[dizzzz]

@vogelsgesang you are right, the community 'rules' are not so clear, when visiting the GitHub pages. Bugs/issues should clearly by filed here, but in many cases it is better to consult the exist-open mailing list first; the best reason is: there are more ppl subscribed to exist-open thnat to the issue tracker,

anyway, your report has been picked up, thnx for filing; we;ll address it.

for the time being (name might change)

• https://github.com/wolfgangmm/monex (latest)
  and
• https://github.com/wolfgangmm/monex/releases (not the latest)