Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #1217 (new)

Opened 11 years ago

Last modified 3 years ago

Projected Image sha1

Reported by: jburel Owned by:
Priority: major Milestone: GatherReqs
Component: Services Version: n.a.
Keywords: n.a. Cc: jamoore, mtbcarroll
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

sha1 not created for the projected image. "pending" in DB

Change History (16)

comment:1 Changed 10 years ago by cxallan

  • Milestone changed from Unscheduled to OMERO-Beta4.1
  • Status changed from new to assigned
  • Version 3.0-M1 deleted

comment:2 Changed 10 years ago by cxallan

  • Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2

comment:3 Changed 9 years ago by jburel

  • Milestone changed from OMERO-Beta4.2 to Unscheduled

not top priority pushing

comment:4 Changed 5 years ago by jburel

  • Cc jamoore mtbcarroll added
  • Milestone changed from Unscheduled to 5.1.0
  • Status changed from assigned to new

Moving to 5.1.0 for consideration. Pending is still entered in the DB

comment:5 Changed 5 years ago by jburel

  • Owner cxallan deleted

comment:6 Changed 5 years ago by jamoore

for reference, "Pending..." in ome/services/PixelsImpl.java

comment:7 Changed 5 years ago by mtbcarroll

Interesting scoping questions here. For instance, ought there be a choice of checksum algorithm? Is it still important to hash the pixel values if we switch to having a Bio-Formats reader for Pixels files and turn these images into more like a normal FS image with a file hash? Are we likely to do that anyway?

comment:8 Changed 5 years ago by jamoore

  • initially, no choice.
  • you could still use the hash if we migrated to an OriginalFile?, so that's fine.
  • not *highly* likely that we'll do the pixels reader, but we'll have to better scope 5.2 for that.

comment:9 Changed 5 years ago by jamoore

  • Milestone changed from 5.1.0 to 5.1.1

comment:10 Changed 5 years ago by jamoore

  • Milestone changed from 5.1.1 to 5.2.0-m1

I could imagine a fix for 5.1.2 but it won't be as flexible or clear as we'd like it to be (needing a DB upgrade to make sha1 --> hash nullable). Since we've spent time disabling sha1'ing for 5.1, pushing to 5.2, so we don't undo our work.

comment:11 Changed 4 years ago by jamoore

  • Milestone changed from 5.2.0 to OMERO-5.2.0

Splitting due to milestone decoupling.

comment:12 Changed 4 years ago by jamoore

  • Milestone changed from OMERO-5.2.0 to OMERO-5.2.1

comment:13 Changed 4 years ago by jburel

  • Milestone changed from OMERO-5.2.1 to OMERO-5.2.2

Milestone OMERO-5.2.1 deleted

comment:14 Changed 4 years ago by jburel

  • Milestone changed from OMERO-5.2.2 to OMERO-5.2.1

Milestone OMERO-5.2.2 deleted

comment:15 Changed 4 years ago by jburel

  • Milestone changed from OMERO-5.2.2 to GatherReqs

comment:16 Changed 3 years ago by jburel

Something to consider for 5.3 i.e. DB cleanup

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.83493 sec.)

We're Hiring!