Hi Daniel,
given the 1001 configuration mosaic has, it's sometimes hard to say what
expected behavior for a particular
layout is, that said, what is happening makes sense to me:
- On first upload configure=none just makes GeoServer not try to open
the reader (which would trigger its normal startup, that is, harvesting)
- On first harvest the code has to grab the reader to perform the
harvest, that in the case of mosaic triggers the "auto-magic"
configuration, which is, harvest what you've been told to harvest and get
ready to serve back imagery
So yes, adding "CanBeEmpty=true" in the configuration and pointing the
mosaic to directory without data is pretty much the only way to
prevent a full harvest. To me, that's expected behavior.
Cheers
Andrea
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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
