Open GoogleCodeExporter opened 9 years ago
Hm, sorry we didn't see this issue until now.
The only reason schema v1 code is in sqlog is for backwards compatibility,
and I think the idea would be to remove v1 support after everyone has upgraded.
Therefore, I don't think that adding an option to force v1 would be a good idea.
However, the function to create the v1 table and backfill it with existing jobs
is still in sqlog-db-util (backfill_slurm_joblog_table_to_v1), so you could
modify
sqlog-db-util to call that function and create your v1 table.
If there is not a v2 table in the DB, then the rest of the sqlog tools should
fall
back to v1 (for now).
mark
Original comment by mark.gro...@gmail.com
on 26 Apr 2011 at 1:31
Original issue reported on code.google.com by
hadi.sha...@gmail.com
on 18 Apr 2011 at 7:18