On Tue, Feb 5, 2019 at 2:12 PM Arnaud L. <arnaud.lis...@codata.eu> wrote:
> Just a note, I don't know whether this is a bug or something missing in > the documentation, or maybe even something I have overlooked : > the "schema" parameter in the Datastore Configuration page does not seem > to have any effect. > Hum... the schema in the datastore configuration should affect only the feature types served by the datastore itself. Are you expecting it to affect the mosaics somehow? Did you setup any connection between the datastore config and the mosaic? > In the datastore.properties of each mosaic (and of my imagepyramid) I > added "schema=myschema", and everything worked perfectly afterwards. > Is the the expected behaviour ? Should I propose a quick patch in the > jndi configuration doc ? > I think it's the expected behavior, but without seeing if there is any connection between the mosaic and the store page in the UI I cannot comment further > Also for my datastore.properties file, I had followed the guide from the > "geoserver training" section of your website : > > https://geoserver.geo-solutions.it/edu/en/multidim/imagemosaic/mosaic_datastore.html#using-a-jndi-connection-pool > which did not mention this "schema" parameter, so mabe I could add this > somewhere ? > I'm afraid not, while the generated output of the training material is under a creative commons license, the source code of it is in a private repo. But it's a good suggestion, I've opened a ticket to remind us a fix the next time we work on the material. Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
