Doc on uPortal-index feature
Julien Gribonvald
Hi folks,
I didn't find a doc on the uPortal-indexing, after watching really quickly on following are my questions/thoughts :
- We can't set the directory of file indexing generated outside
of the deployed app. Why not using something like Resource that
permit to use a classpath/file path ? Or maybe having a
@ConditionalOnMissingBean on beans to be able to customize where
to define the path of Indexed files ?
- To disabling the feature it seems that we need to set the property 'org.apereo.portal.index.relativePath' to null, but it's not possible from properties file. Why not disabling this feature by default ? My problem is that is getting more and more space days after days (not a lot, but it's growing...) and I fear that we may have a disk space problem due to that (when using several cms portlet). What do you think about defining the default value to null and having the property set into uPortal-start, like that everybody can disable the feature easily. My problem is that the new feature is enable by default without possibility to disable it. Any thought ?
- More generally when a i18n key is added only US translation are
provided, that's ok nobody can't know all language, but we should
find a way to trace / to open an issue or something to request the
help of the community to get keys translated quickly to permit
easily to follow features and versions ! It's a bad thing when you
try to follow uPortal version with uPortal-start, that after you
deployed the new last version and that finally you get keys not
translated on your language whereas nearly all other things are,
and more you need to watch on which i18n keys that are not
translated.
On an other hand if you need a French Translation you can ask me
or any other French people (like Christian Cousquer) on slack !
Thanks,
Julien Gribonvald
Julien Gribonvald
Sorry I sent my mail too quickly !
We can set the property 'org.apereo.portal.index.relativePath'
to null, but we have to set it like that:
org.apereo.portal.index.relativePath=#{null}, but I think it would
be better if the default state would be disabled. Also even
setting this value to disabled index files are created at the run
and I see the log o.a.portal.index.PortalSearchIndexer 2019-09-27
12:07:01,900 - Search indexing is DISABLED based on presence or
absence of a Directory
Julien
--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uportal-dev...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/cbb234c4-d4a8-1c35-b5a1-cba4aaecb504%40recia.fr.
Julien Gribonvald
Jonathan M. Tran
We're doing something similar at the moment because the files/folders are not owned by the user that Tomcat runs as.
I managed to disable it by setting org.apereo.portal.index.relativePath to a path that doesn't exist such as
../../temp/index (I was hoping that I could have it write to ${CATALINA_HOME}/temp/index), but I like
#{null} better.
I've documented this in
https://github.com/Jasig/uPortal/pull/1880. Any suggestions on the verbiage are welcome
- Jonathan
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/5977a41c-98f5-b8ea-a7fa-93aad9fbeb45%40recia.fr.
Julien Gribonvald
@Jonathan: Good thing to push a doc, you did more things than me ;)
After I think that we can make a better management on this property between uPortal sources and uPortal-start, like having this option disable by default on uPortal sources and activating it on uPortal-start. But is there any thought ?
- Julien
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/9bb5f2e3-69b9-6cb6-e581-f0736d0712a7%40cpp.edu.
Julien Gribonvald