Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#546 closed defect (fixed)

rasdaman version in petascope.properties

Reported by: pcampalani Owned by: pcampalani
Priority: minor Milestone: 9.0
Component: petascope Version: development
Keywords: rasdaman version Cc: dmisev
Complexity: Easy

Description

Currently the version is outdated (still to 8.3), should be updated to e.g. the current git-tag 'v9.0.0-beta1'.

Although the variable (used simply for logging by Petascope, by now) is of kind "need to adapt" -- hence the user should care about its value -- we should provide updated defaults, maybe with an automated mechanism (?).

Change History (6)

comment:1 Changed 4 years ago by dmisev

I suggest we remove it, I don't see the value of this parameter. We should maybe add some command in rasdaman that prints the rasdaman version and use that, like SELECT version() in PostgreSQL for example.

comment:2 Changed 4 years ago by dmisev

Consider #549, after that patch is applied, petascope could ping rasdaman with 'select version()' at startup to determine the version.

comment:3 Changed 4 years ago by pcampalani

  • Status changed from new to accepted

comment:4 Changed 4 years ago by pcampalani

  • Resolution set to fixed
  • Status changed from accepted to closed

Fixed in changeset:aa80764.

comment:5 Changed 3 years ago by dmisev

When using an older rasdaman that has no support for version() petascope fails to start; patch submitted.

comment:6 Changed 3 years ago by pcampalani

rasdaman version logging from Petascope was accidentally removed in changeset:2988467, then restored in changeset:a8d9e4e.

Note: See TracTickets for help on using tickets.