I just upgraded to v0.32.5 and noticed two issues that are minor, but that I’d like to suggest be mentioned in the docs.
I am running the .jar version, on linux; I rename the jars to indicate their version and then have a symbolic link named simply “metabase.jar” that points to the version I wish to be running. For some inane reason, when I renamed the jars, I got in the habit of NOT ending the filename with “.jar” after the version number. This worked fine in previous versions. However, in 0.32.5 it generated fatal errors of type “FileNotFoundException”… the file reported unfound was the jar itself (the physical name, not the link name). Simply renaming the JARs by appending “.jar” to the physical filename (and updating the link) solved the problem.
In other words, beginning with 0.32 the jar filename must end with .jar. That is definitely not a bug, but because it was not true before I’d like to see it mentioned/footnoted in the docs.
Secondly, it didn’t use to matter what the default directory was when starting the jar. Now it does in that the working directory will have the plugins folder created in it. Since I previously had a startup script in my path, I started it from any arbitrary location; the new version litters my drive with plugin directories. This is, IMO, also worth mentioning in the install notes.
Thanks for listening, and for such a great product!