Ticket #15 (closed defect: fixed)

Opened 9 months ago

Last modified 7 months ago

/metadata should accept PUT/POST

Reported by: mahlon Assigned to: mahlon
Priority: major Milestone: ThingFish 0.2 - The "Butterhand" Release
Component: ThingFish Keywords: thingfish metadata rest
Cc: Depends on:

Description (Last modified by mahlon)

A PUT/POST method to /metadata to upload metadata key/values pairs en masse. This is in addition to the individual '/metadata/uuid/key' POSTs, and can be used to avoid a bunch of rapid hits to the server when making lots of metadata changes.

Exact format of required body entity to be determined.

POST /metadata
A list of UUIDs and associated tuples, will replace all metadata outright
PUT /metadata
A list of UUIDs and associated tuples, will perform updates
POST /metadata/uuid
Replace metadata for a single resource
PUT /metadata/uuid
Update metadata for a single resource

Change History

11/29/07 21:39:13 changed by mahlon

  • keywords changed from thingfish documentation metadata to thingfish metadata rest.

12/20/07 07:51:11 changed by mahlon

  • description changed.

01/22/08 08:55:46 changed by mahlon

  • owner changed from mgranger to mahlon.
  • status changed from new to assigned.

02/01/08 23:27:12 changed by mahlon

(In [429]) * Checkpoint commit of metastore updates via the /metadata handler. Refs #15.

  • Added new metastore APIs: has_uuid?(), set_properties(), and added to all current metastores.
  • Currently just does PUT to /metadata/uuid/key and /metadata/uuid. More to come.

02/01/08 23:29:10 changed by mahlon

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [447]) * Add request parsing for JSON filter.

  • Add tests for incoming JSON/YAML filters.
  • Convenience accessors for request/response content-types
  • This commit closes #15 and makes the SimpleMetadata? handler functionally complete! Wooo hoo!!