[#SAK-10801] Add contextId (siteId) field to Event

Sakai

Add contextId (siteId) field to Event

Created: 19-Jul-2007 01:59 Updated: 07-Aug-2008 18:50

Component/s:

Event (SVN module)

Affects Version/s:

2.0, 1.0, 1.5.0, 1.5.1, trunk [DO NOT USE], 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.1.x, 2.2.0, 2.2.1, 2.3.0, 2.2.2, 2.2.x, 2.4.0, 2.3.x, 2.5.0, 2.3.1, 2.2.3, 2.4.x, 2.4.1, 2.5.2

Fix Version/s:

2.6.0

Time Tracking:

Not Specified

File Attachments:

SAK-10801.patch (6 kb)
2.

search.diff (1 kb)

Environment:

Any

Issue Links:

Relate

This issue relates to:

SAK-13809 Event.getContext() returns null for Presence events

2.4.x Status:	None
2.5.x Status:	None

Description

« Hide

Currently, there is no efficient and deterministic way to know in which context (siteId) an event was generated. The current work-around for this is to parse the Ref field and try to guess the context.

Events can be sakai scoped (with new contextId field set to null) or site scoped (contextId set to siteId). This would probably involve adding a column to SAKAI_EVENT and a setter a getter for it in the Event class.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Lance Speelmon - 29-Jul-2007 09:24

IU needs this implemented by August 16th, 2007 for a production roll out of Site Stats. Andrew will work with Glenn to make it happen. Thanks, L

[ Permlink | « Hide ]

Andrew Poland - 07-Aug-2007 14:08

Here's a first attempt that is based on the reference parsing functions that Nuno wrote into sitestats.

Certainly we want to provide a cleaner implementation for 2.5, however Oncourse will be using this to get things rolling for our release next week.

This patch will populate a new column in SAKAI_EVENT called CONTEXT:

alter table sakai_event add CONTEXT VARCHAR2(99);

Andrew

[ Permlink | « Hide ]

Nuno Fernandes - 08-Aug-2007 03:18

Please note that the process of filling the new CONTEXT column for existing data in SAKAI_EVENT will not be perfect:

Both EVENT and REF field contents have changed for the same event across Sakai upgrades!

As an example, Message Center have changed their events from content.* to msgcntr.* (content.* are associated with the Resources tool so, were ambiguous) and their references changed the path separator from : to / (more consistent with the remaining events).

[ Permlink | « Hide ]

Stephen Marquard - 06-Jun-2008 12:10

Creating a branch to try out an implementation of this

[ Permlink | « Hide ]

Stephen Marquard - 08-Jun-2008 09:30

Patch for search (mock service)

[ Permlink | « Hide ]

Stephen Marquard - 14-Jun-2008 11:07

Resolved in trunk: r47466:47469 (event, search, memory, reference)

[ Permlink | « Hide ]

Stephen Marquard - 15-Jun-2008 07:26

And 47471,47472 (entitybroker, content)

[ Permlink | « Hide ]

Megan May - 07-Aug-2008 18:50

removing the 2.5.x merge status as branch managers discussion determined this a fairly substantial change in functionality and thus, didn't meet the criteria for 2.5.x