blob: 2bc4f3c5fba1c349149e5bd875d022ca225ff4d1 [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="keywords" content="SMILA/Specifications/ProcessingMessageResequencer,SMILA/Specifications/Processing Message Resequencer/Connectivity Consolidation Buffer,SMILA/Specifications/Processing Message Resequencer/Full Resequencer,SMILA/Specifications/Processing Message Resequencer/Record Version Number,SMILA/Specifications/Processing Message Resequencer/Skip Pipelet,SMILA/Specifications/Processing Message Resequencer/Smart Resequencer" />
<link rel="shortcut icon" href="http://wiki.eclipse.org/SMILA/Specifications/favicon.ico" />
<link rel="search" type="application/opensearchdescription+xml" href="http://wiki.eclipse.org/opensearch_desc.php" title="Eclipsepedia (English)" />
<link rel="alternate" type="application/rss+xml" title="Eclipsepedia RSS Feed" href="http://wiki.eclipse.org/index.php?title=Special:Recentchanges&amp;feed=rss" />
<link rel="alternate" type="application/atom+xml" title="Eclipsepedia Atom Feed" href="http://wiki.eclipse.org/index.php?title=Special:Recentchanges&amp;feed=atom" />
<title>SMILA/Specifications/ProcessingMessageResequencer - Eclipsepedia</title>
<style type="text/css" media="screen,projection">/*<![CDATA[*/ @import "/skins/eclipsenova/novaWide.css?116"; /*]]>*/</style>
<link rel="stylesheet" type="text/css" media="print" href="http://wiki.eclipse.org/skins/eclipsenova/eclipsenovaPrint.css?116" />
<link rel="stylesheet" type="text/css" media="handheld" href="http://wiki.eclipse.org/skins/eclipsenova/handheld.css?116" />
<link rel="stylesheet" type="text/css" href="http://wiki.eclipse.org/skins/eclipsenova/Nova/css/header.css" media="screen" />
<link rel="stylesheet" type="text/css" href="http://wiki.eclipse.org/skins/eclipsenova/tabs.css" media="screen" />
<link rel="stylesheet" type="text/css" href="http://wiki.eclipse.org/skins/eclipsenova/Nova/css/visual.css" media="screen" />
<link rel="stylesheet" type="text/css" href="http://wiki.eclipse.org/skins/eclipsenova/Nova/css/layout.css" media="screen" />
<link rel="stylesheet" type="text/css" href="http://wiki.eclipse.org/skins/eclipsenova/Nova/css/footer.css" media="screen" />
<!--[if IE]><link rel="stylesheet" type="text/css" href="/skins/eclipsenova/IEpngfix.css" media="screen" /><![endif]-->
<!--[if lt IE 5.5000]><style type="text/css">@import "/skins/eclipsenova/IE50Fixes.css?116";</style> <![endif]-->
<!--[if IE 5.5000]><style type="text/css">@import "/skins/eclipsenova/IE55Fixes.css?116";</style><![endif]-->
<!--[if IE 6]><style type="text/css">@import "/skins/eclipsenova/IE60Fixes.css?116";</style><![endif]-->
<!--[if IE 7]><style type="text/css">@import "/skins/eclipsenova/IE70Fixes.css?116";</style><![endif]-->
<!--[if lt IE 7]><script type="text/javascript" src="/skins/common/IEFixes.js?116"></script>
<meta http-equiv="imagetoolbar" content="no" /><![endif]-->
<script type= "text/javascript">/*<![CDATA[*/
var skin = "eclipsenova";
var stylepath = "/skins";
var wgArticlePath = "/$1";
var wgScriptPath = "";
var wgScript = "/index.php";
var wgServer = "http://wiki.eclipse.org";
var wgCanonicalNamespace = "";
var wgCanonicalSpecialPageName = false;
var wgNamespaceNumber = 0;
var wgPageName = "SMILA/Specifications/ProcessingMessageResequencer";
var wgTitle = "SMILA/Specifications/ProcessingMessageResequencer";
var wgAction = "view";
var wgRestrictionEdit = [];
var wgRestrictionMove = [];
var wgArticleId = "21687";
var wgIsArticle = true;
var wgUserName = null;
var wgUserGroups = null;
var wgUserLanguage = "en";
var wgContentLanguage = "en";
var wgBreakFrames = false;
var wgCurRevisionId = "174141";
var wgVersion = "1.12.0";
var wgEnableAPI = true;
var wgEnableWriteAPI = false;
/*]]>*/</script>
<script type="text/javascript" src="http://wiki.eclipse.org/skins/common/wikibits.js?116"><!-- wikibits js --></script>
<!-- Performance mods similar to those for bug 166401 -->
<script type="text/javascript" src="http://wiki.eclipse.org/index.php?title=-&amp;action=raw&amp;gen=js&amp;useskin=eclipsenova"><!-- site js --></script>
<!-- Head Scripts -->
<script type="text/javascript" src="http://wiki.eclipse.org/skins/common/ajax.js?116"></script>
<link rel="stylesheet" type="text/css" href="ProcessingMessageResequencer.html" /> </head>
<body class="mediawiki ns-0 ltr page-SMILA_Specifications_ProcessingMessageResequencer">
<div id="globalWrapper">
<div id="column-one">
<!-- Eclipse Additions for the Top Nav start here M. Ward-->
<div id="header">
<div id="header-graphic">
<img src="http://wiki.eclipse.org/skins/eclipsenova/eclipse.png" alt="Eclipse Wiki">
</div>
<!-- Pulled 101409 Mward -->
<div class="portlet" id="p-personal">
<div class="pBody">
<ul>
<li id="pt-login"><a href="http://wiki.eclipse.org/index.php?title=Special:Userlogin&amp;returnto=SMILA/Specifications/ProcessingMessageResequencer">Log in</a></li>
</ul>
</div>
</div>
<div id="header-icons">
<div id="sites">
<ul id="sitesUL">
<li><a href="http://www.eclipse.org"><img src="http://dev.eclipse.org/custom_icons/eclipseIcon.png" width="28" height="28" alt="Eclipse Foundation" title="Eclipse Foundation" /><div>Eclipse Foundation</div></a></li>
<li><a href="http://marketplace.eclipse.org"><img src="http://dev.eclipse.org/custom_icons/marketplace.png" width="28" height="28" alt="Eclipse Marketplace" title="Eclipse Marketplace" /><div>Eclipse Marketplace</div></a></li>
<li><a href="https://bugs.eclipse.org/bugs"><img src="http://dev.eclipse.org/custom_icons/system-search-bw.png" width="28" height="28" alt="Bugzilla" title="Bugzilla" /><div>Bugzilla</div></a></li>
<li><a href="http://live.eclipse.org"><img src="http://dev.eclipse.org/custom_icons/audio-input-microphone-bw.png" width="28" height="28" alt="Live" title="Live" /><div>Eclipse Live</div></a></li>
<li><a href="http://planeteclipse.org"><img src="http://dev.eclipse.org/large_icons/devices/audio-card.png" width="28" height="28" alt="PlanetEclipse" title="Planet" /><div>Planet Eclipse</div></a></li>
<li><a href="http://portal.eclipse.org"><img src="http://dev.eclipse.org/custom_icons/preferences-system-network-proxy-bw.png" width="28" height="28" alt="Portal" title="Portal" /><div>My Foundation Portal</div></a></li>
</ul>
</div>
</div>
</div>
<!-- NEW HEADER STUFF HERE -->
<div id="header-menu">
<div id="header-nav">
<ul> <li><a class="first_one" href="http://wiki.eclipse.org/" target="_self">Home</a></li> <li><a href="http://www.eclipse.org/downloads/" target="_self">Downloads</a></li>
<li><a href="http://www.eclipse.org/users/" target="_self">Users</a></li>
<li><a href="http://www.eclipse.org/membership/" target="_self">Members</a></li>
<li><a href="http://wiki.eclipse.org/index.php/Development_Resources" target="_self">Committers</a></li>
<li><a href="http://www.eclipse.org/resources/" target="_self">Resources</a></li>
<li><a href="http://www.eclipse.org/projects/" target="_self">Projects</a></li>
<li><a href="http://www.eclipse.org/org/" target="_self">About Us</a></li>
</ul>
</div>
<div id="header-utils">
<!-- moved the search window here -->
<form action="http://wiki.eclipse.org/Special:Search" >
<input class="input" name="search" type="text" accesskey="f" value="" />
<input type='submit' onclick="this.submit();" name="go" id="searchGoButton" class="button" title="Go to a page with this exact name if one exists" value="Go" />&nbsp;
<input type='submit' onclick="this.submit();" name="fulltext" class="button" id="mw-searchButton" title="Search Eclipsepedia for this text" value="Search" />
</form>
</div>
</div>
<!-- Eclipse Additions for the Header stop here -->
<!-- Additions and mods for leftside nav Start here -->
<!--Started nav rip here-->
<!-- these are the nav controls main page, changes etc -->
<div id="novaContent" class="faux">
<div id="leftcol">
<ul id="leftnav">
<!-- these are the page controls, edit history etc -->
<li class="separator"><a class="separator">Navigation &#160;&#160;</li>
<li id="n-mainpage"><a href="http://wiki.eclipse.org/Main_Page">Main Page</a></li>
<li id="n-portal"><a href="http://wiki.eclipse.org/Eclipsepedia:Community_Portal">Community portal</a></li>
<li id="n-currentevents"><a href="http://wiki.eclipse.org/Eclipsepedia:Current_events">Current events</a></li>
<li id="n-recentchanges"><a href="http://wiki.eclipse.org/Special:Recentchanges">Recent changes</a></li>
<li id="n-randompage"><a href="http://wiki.eclipse.org/Special:Random">Random page</a></li>
<li id="n-help"><a href="http://wiki.eclipse.org/Help:Contents">Help</a></li>
<li class="separator"><a class="separator">Toolbox &#160;&#160;</a></li>
<li id="t-whatlinkshere"><a href="http://wiki.eclipse.org/Special:Whatlinkshere/SMILA/Specifications/ProcessingMessageResequencer">What links here</a></li>
<li id="t-recentchangeslinked"><a href="http://wiki.eclipse.org/Special:Recentchangeslinked/SMILA/Specifications/ProcessingMessageResequencer">Related changes</a></li>
<!-- This is the toolbox section -->
<li id="t-upload"><a href="http://wiki.eclipse.org/Special:Upload">Upload file</a></li>
<li id="t-specialpages"><a href="http://wiki.eclipse.org/Special:Specialpages">Special pages</a></li>
<li id="t-print"><a href="http://wiki.eclipse.org/index.php?title=SMILA/Specifications/ProcessingMessageResequencer&amp;printable=yes">Printable version</a></li> <li id="t-permalink"><a href="http://wiki.eclipse.org/index.php?title=SMILA/Specifications/ProcessingMessageResequencer&amp;oldid=174141">Permanent link</a></li> </ul>
</div>
<!-- Additions and mods for leftside nav End here -->
<div id="column-content">
<div id="content">
<a name="top" id="top"></a>
<div id="tabs">
<ul class="primary">
<li class="active"><a href="ProcessingMessageResequencer.html"><span class="tab">Page</span></a></li>
<li><a href="http://wiki.eclipse.org/index.php?title=Talk:SMILA/Specifications/ProcessingMessageResequencer&amp;action=edit"><span class="tab">Discussion</span></a></li>
<li><a href="http://wiki.eclipse.org/index.php?title=SMILA/Specifications/ProcessingMessageResequencer&amp;action=edit"><span class="tab">View source</span></a></li>
<li><a href="http://wiki.eclipse.org/index.php?title=SMILA/Specifications/ProcessingMessageResequencer&amp;action=history"><span class="tab">History</span></a></li>
<li><a href="http://wiki.eclipse.org/index.php?title=Special:Userlogin&amp;returnto=SMILA/Specifications/ProcessingMessageResequencer"><span class="tab">Edit</span></a></li>
</ul>
</div>
<script type="text/javascript"> if (window.isMSIE55) fixalpha(); </script>
<h1 class="firstHeading">SMILA/Specifications/ProcessingMessageResequencer</h1>
<div id="bodyContent">
<h3 id="siteSub">From Eclipsepedia</h3>
<div id="contentSub"><span class="subpages">&lt; <a href="../../SMILA.html" title="SMILA">SMILA</a> | <a href="../Specifications.1.html" title="SMILA/Specifications">Specifications</a></span></div>
<div id="jump-to-nav">Jump to: <a href="ProcessingMessageResequencer.html#column-one">navigation</a>, <a href="ProcessingMessageResequencer.html#searchInput">search</a></div> <!-- start content -->
<p>
</p>
<div class="messagebox" style="background-color: #def3fe; border: 1px solid #c5d7e0; color: black; padding: 5px; margin: 1ex 0; min-height: 35px; padding-left: 45px;">
<div style="float: left; margin-left: -40px;"><a href="http://wiki.eclipse.org/Image:Note.png" class="image" title="Note.png"><img alt="" src="http://wiki.eclipse.org/images/c/cc/Note.png" width="35" height="35" border="0" /></a></div>
<div><b>Status</b><br />this page is very much a WIP and discussion is still happening on the <a href="http://dev.eclipse.org/mhonarc/lists/smila-dev/msg00608.html" class="external text" title="http://dev.eclipse.org/mhonarc/lists/smila-dev/msg00608.html" rel="nofollow">dev list</a>.
<ul><li> 2009 10 02 major changes to reflect newest insights
</li></ul>
<p>as the concept matures during the discussion this page will be updated in certain intervals.
</p><p>this enhancement is tracked thru <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=289995" class="external text" title="https://bugs.eclipse.org/bugs/show_bug.cgi?id=289995" rel="nofollow">bug 289995</a>
</p>
for the development i opened a new branch @ <a href="https://dev.eclipse.org/svnroot/rt/org.eclipse.smila/branches/2009-09-23_r608_resequencer" class="external free" title="https://dev.eclipse.org/svnroot/rt/org.eclipse.smila/branches/2009-09-23_r608_resequencer" rel="nofollow">https://dev.eclipse.org/svnroot/rt/org.eclipse.smila/branches/2009-09-23_r608_resequencer</a></div>
</div>
<table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1"><a href="ProcessingMessageResequencer.html#The_Core_Problem"><span class="tocnumber">1</span> <span class="toctext">The Core Problem</span></a></li>
<li class="toclevel-1"><a href="ProcessingMessageResequencer.html#Indexing_Requirements"><span class="tocnumber">2</span> <span class="toctext">Indexing Requirements</span></a>
<ul>
<li class="toclevel-2"><a href="ProcessingMessageResequencer.html#Functional"><span class="tocnumber">2.1</span> <span class="toctext">Functional</span></a>
<ul>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#Basic_Operations"><span class="tocnumber">2.1.1</span> <span class="toctext">Basic Operations</span></a></li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#compound_management.2C_splitting_of_records"><span class="tocnumber">2.1.2</span> <span class="toctext">compound management, splitting of records</span></a>
<ul>
<li class="toclevel-4"><a href="ProcessingMessageResequencer.html#Composition"><span class="tocnumber">2.1.2.1</span> <span class="toctext">Composition</span></a></li>
<li class="toclevel-4"><a href="ProcessingMessageResequencer.html#Aggregation"><span class="tocnumber">2.1.2.2</span> <span class="toctext">Aggregation</span></a></li>
<li class="toclevel-4"><a href="ProcessingMessageResequencer.html#Parent.2FDescendants_Ordering__Requirement"><span class="tocnumber">2.1.2.3</span> <span class="toctext">Parent/Descendants Ordering Requirement</span></a></li>
</ul>
</li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#support_.3E1_processing_targets"><span class="tocnumber">2.1.3</span> <span class="toctext">support &gt;1 processing targets</span></a></li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#complex_processing_chains"><span class="tocnumber">2.1.4</span> <span class="toctext">complex processing chains</span></a></li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#parallel_processing_branches"><span class="tocnumber">2.1.5</span> <span class="toctext">parallel processing branches</span></a></li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#clustering"><span class="tocnumber">2.1.6</span> <span class="toctext">clustering</span></a></li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#oscillating_items"><span class="tocnumber">2.1.7</span> <span class="toctext">oscillating items</span></a></li>
</ul>
</li>
<li class="toclevel-2"><a href="ProcessingMessageResequencer.html#Non_-_Functional"><span class="tocnumber">2.2</span> <span class="toctext">Non - Functional</span></a>
<ul>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#single_point_of_failure"><span class="tocnumber">2.2.1</span> <span class="toctext">single point of failure</span></a></li>
<li class="toclevel-3"><a href="ProcessingMessageResequencer.html#scalability_and_performance"><span class="tocnumber">2.2.2</span> <span class="toctext">scalability and performance</span></a></li>
</ul>
</li>
</ul>
</li>
<li class="toclevel-1"><a href="ProcessingMessageResequencer.html#Solution_Proposals"><span class="tocnumber">3</span> <span class="toctext">Solution Proposals</span></a></li>
<li class="toclevel-1"><a href="ProcessingMessageResequencer.html#General_Problems"><span class="tocnumber">4</span> <span class="toctext">General Problems</span></a>
<ul>
<li class="toclevel-2"><a href="ProcessingMessageResequencer.html#Shared_Record_Instance_via_Blackboard"><span class="tocnumber">4.1</span> <span class="toctext">Shared Record Instance via Blackboard</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="ProcessingMessageResequencer.html#Appendix"><span class="tocnumber">5</span> <span class="toctext">Appendix</span></a>
<ul>
<li class="toclevel-2"><a href="ProcessingMessageResequencer.html#Abreviations"><span class="tocnumber">5.1</span> <span class="toctext">Abreviations</span></a></li>
<li class="toclevel-2"><a href="ProcessingMessageResequencer.html#Ideas"><span class="tocnumber">5.2</span> <span class="toctext">Ideas</span></a></li>
</ul>
</li>
</ul>
</td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
<a name="The_Core_Problem"></a><h3> <span class="mw-headline"> The Core Problem </span></h3>
<p>When listening with &gt;1 listener on a Q or with selectors there is no guarantee that the order of processing requests (PR) is maintained as intended. However, at the end of processing we need to be sure that the final processing target reflects the correct state of the data source at any given time.
</p><p>The needs of the final processing target might differ in their requirements. At this time we will only treat the case of a full text retrieval engines, like Lucene.
</p><p>SMILA/Specifications/ProcessingMessageResequencer
</p>
<a name="Indexing_Requirements"></a><h3> <span class="mw-headline"> Indexing Requirements </span></h3>
<p>the requirements for indexing are a little relaxed compared to the general case. These are the simplifications:
</p>
<ul><li> the order needs only to be maintained on a per record base
</li><li> older PRs are always superseded by newer PR for a given resource. the outcome of these operations can be discarded -- or even better: processing of these could be suppressed.
</li></ul>
<p>The following requirements are just a complete list of possible demands an application may impose. There is no implicit statement attached to the likelihood that a particular requirement is requested by an application, although there might be such. The intent of the list is to have a complete enumeration. qualification for an item is merely: may such a case, however unlikely, exist?
</p><p>The solutions are to outline how a specific requirement may be implemented or covered. It also may chose to not cover it. An application may then chose a solution that matches its needs. As usual the requirements are split into functional and non-functional.
</p>
<a name="Functional"></a><h4> <span class="mw-headline"> Functional </span></h4>
<a name="Basic_Operations"></a><h5> <span class="mw-headline"> Basic Operations </span></h5>
<table width="100%" style="font-family: Trebuchet MS;vertical-align:text-top;" border="1">
<tr style="font-weight:bold;font-size:larger;color:white;background:gray;text-align:center;">
<td> Operation N </td><td> Operation N+1 </td><td> expected index State after N+1
</td></tr>
<tr>
<td> ADD A,t1 </td><td> ADD A,t2 </td><td> A,t2
</td></tr>
<tr>
<td> ADD A,t1 </td><td> DELETE A,t2 </td><td> A doesn't exist
</td></tr>
<tr>
<td> DELETE A,t1 </td><td> ADD A,t2 </td><td> A exists
</td></tr></table>
<p>the following sections names the cases/scenarios that need to be covered that dont come to mind mediately but need to be considered nonetheless:
</p>
<a name="compound_management.2C_splitting_of_records"></a><h5> <span class="mw-headline"> compound management, splitting of records </span></h5>
<p>two cases of compounds need to be distinguished here: aggregations and compositions.
</p><p>as in UML, aggregation means that the parent has a dependency to the child but the child may exist (as a child or even distinctly on its own) elsewhere. composition in contrast <b>owns</b> the descendants, meaning that they cant be accessed or created independent of the parent. life cycle of the child is controlled by the parent.
the two cases will be discussed in the context of processing now:
</p>
<a name="Composition"></a><h6> <span class="mw-headline"> Composition </span></h6>
<p>this is the easier case for resquencing b/c only the one processing step working on the root item is possible to create PRs for child item. the ID of a child item will always include the parent id in some sort of way. thus resequencing the parent and its children as a whole is sufficient. (an internal ordering of parent and descendants may be required and is discussed below.)
</p>
<a name="Aggregation"></a><h6> <span class="mw-headline"> Aggregation </span></h6>
<p>the referenced item may be referenced
</p>
<ul><li> by some other item OR
</li><li> may exist on its own.
</li></ul>
<p>as a consequence
</p>
<ul><li> several diff. root items may hold a reference to it OR
</li><li> the child item is being processed as a root itself.
</li></ul>
<p>an application may require to handle these cases in these ways:
</p>
<ol><li> referenced items are to be seen only in context to the parent or on their own. <br />e.g. it does not make it apparent that the child belong to A is in fact the same as belonging to B OR the same root item C . <br />this leads to an identical handling as with compositions and in each case a records is added to the index.
</li><li> referenced items are to be seen as distinct items, making the relationships apparent<br /> in this case the ID is generated always in the same way independently of the parent. Only one record for the child is added to the index. the child record will either contain no reference to the parent(s) or lists all of them.
</li><li> the third way of handling this, is to do both.
</li></ol>
<p>if the application requires
</p>
<ul><li> to handle references as distinct or shared items (2nd and 3rd case) AND
</li><li> child items must be processed at the time of the parent (can happen if no change event is ever fired for the child or accessible),
</li></ul>
<p>... then aggregation poses the more challenging case in regard to resequencing. B/c new items are created during processing by possibly diff. items the parent item cannot be used as means of ordering the child items. Even less so, if the item may also be added on its own w/o a parent. instead there must be some means that created (split) records are ordered in their own realm.
</p>
<a name="Parent.2FDescendants_Ordering__Requirement"></a><h6> <span class="mw-headline"> Parent/Descendants Ordering Requirement </span></h6>
<p>this requirement applies to the case
</p>
<ul><li> where the child is handled in the context of the parent (composition and 1st case aggregation) AND
</li><li> the order of processing of descendants matters.
</li></ul>
<p>depending on the application's need the descends (ie. all records created from one record ) must be processed in a certain order.
</p><p>parent/child associatens ususally result in a tree structure. there are 4 basic ways to traverse a tree, namely:
</p>
<ul><li> root to leaf, breadth first
</li><li> root to leaf, depth first
</li><li> leaf to root, breadth first
</li><li> leaf to root, depth first
</li></ul>
<p>appart from this, applications may have special processing needs and as such an own, custom implementation must be supported.
</p>
<a name="support_.3E1_processing_targets"></a><h5> <span class="mw-headline"> support &gt;1 processing targets </span></h5>
<p>the same record is processed and added to more than one processing target (PT), such as an 2 diff. search indexs, having diff. structures for diff. tasks.
</p>
<ul><li> it is possible and likely that the records for the same resource will look differently.
</li><li> diff. pipleines and branches may be executed to get to the PT
</li><li> some PRs of the same data source may only be added to one PT while other are added to several and others are chose not to be processed at all.
</li></ul>
<a name="complex_processing_chains"></a><h5> <span class="mw-headline"> complex processing chains </span></h5>
<p>the processing chain (or workflow) may be arbitrarily complex with forks and joins, consisting of several pipelines which may contain any number of pipelets. the path a PR travels is controlled by the rules of pipeline listeners and conditions on their pipelets.<br />in the cases of some setups and due to the nature of concurrency, the same PR may undergo complete different processing steps and it is not foreseeable which route it takes (though such a case is likely a misconfiguration).
</p>
<a name="parallel_processing_branches"></a><h5> <span class="mw-headline"> parallel processing branches </span></h5>
<p>in particular, a workflow may also contain parallel processing branches where the same PR is sent several times ( i.e. creating copies of the same PR ) to diff. Qs and/or with diff. JMS properties for consumption by diff. workflows. <br /> a use case for such a scenario is when the items shall be indexed or stored by completely diff. PTs and where the pre-processing steps are different in the two branches.
</p><p>in this case, it is inherent in the parallel workflow design, that several PRs for the same item exists in the workflow for some period of time. this results automatically in write conflicts and bugs when using a shared record, as is now the case with a persisting BB. therefore in such a case only a transient BB is allowed!
</p><p>workarounds lifting this limitation are:
</p>
<ul><li> have a persisting BB per processing branch. an OOB working setup for this is to execute the parallel processing branches on different nodes in a cluster setup or run several SMILA instances on the same box.
</li><li> modify the ID such that it becomes unique for each parallel processing branch
</li><li> implementing the partition concept for the storages, where each parallel branch will have its own partition.
</li></ul>
<a name="clustering"></a><h5> <span class="mw-headline"> clustering </span></h5>
<p>this means the setup where processing is spread to diff. nodes in a cluster. it also includes usage of several MQs and/or piplines.
</p><p><b>Assumption:</b> there is just one instance on just one node to handle all access to the processing target.
</p>
<a name="oscillating_items"></a><h5> <span class="mw-headline"> oscillating items </span></h5>
<p>these are items that constantly change and where the update intervall usually is smaller then it takes to process them.
</p>
<a name="Non_-_Functional"></a><h4> <span class="mw-headline"> Non - Functional </span></h4>
<a name="single_point_of_failure"></a><h5> <span class="mw-headline"> single point of failure </span></h5>
<p>the solution (ideally) doesnt pose an SPOF.
</p>
<a name="scalability_and_performance"></a><h5> <span class="mw-headline"> scalability and performance </span></h5>
<p>this is a general requirement and the solution shall outline under this section the impact on performance and where possible bottlenecks are.
</p>
<a name="Solution_Proposals"></a><h3> <span class="mw-headline"> Solution Proposals </span></h3>
<ul><li> <a href="Processing_Message_Resequencer/Connectivity_Consolidation_Buffer.html" title="SMILA/Specifications/Processing Message Resequencer/Connectivity Consolidation Buffer"> Connectivity Consolidation Buffer (CBC)</a>
</li><li> <a href="Processing_Message_Resequencer/Full_Resequencer.html" title="SMILA/Specifications/Processing Message Resequencer/Full Resequencer"> Full Resequencer (FRS)</a>
</li><li> <a href="Processing_Message_Resequencer/Smart_Resequencer.html" title="SMILA/Specifications/Processing Message Resequencer/Smart Resequencer"> Smart Resequencer (SRS)</a>
</li><li> <a href="Processing_Message_Resequencer/Skip_Pipelet.html" title="SMILA/Specifications/Processing Message Resequencer/Skip Pipelet">Skip Pipelet (SP)</a>
</li><li> <a href="Processing_Message_Resequencer/Record_Version_Number.html" title="SMILA/Specifications/Processing Message Resequencer/Record Version Number">Record Version Number (RVN)</a>
</li></ul>
<a name="General_Problems"></a><h3> <span class="mw-headline"> General Problems </span></h3>
<a name="Shared_Record_Instance_via_Blackboard"></a><h4> <span class="mw-headline"> Shared Record Instance via Blackboard </span></h4>
<p>sharing the records via the BB for all processing steps introduces a grave concurrency bug. this is outlined in my mail @ [<a href="http://dev.eclipse.org/mhonarc/lists/smila-dev/msg00618.html" class="external text" title="http://dev.eclipse.org/mhonarc/lists/smila-dev/msg00618.html" rel="nofollow">RE: Message Resequencer&nbsp;:: concept bug detected and general SMILA concurrency problem</a>]
</p><p>for the time being using a transient BB should solve the problem but is really not the ideal solution. in the end we need partitions for the BB that solve this issue IMO.
</p>
<a name="Appendix"></a><h3> <span class="mw-headline"> Appendix </span></h3>
<a name="Abreviations"></a><h4> <span class="mw-headline"> Abreviations </span></h4>
<table width="100%" style="font-family: Trebuchet MS;vertical-align:text-top;" border="1">
<tr style="font-weight:bold;font-size:larger;color:white;background:gray;text-align:center;">
<td> Abrev </td><td> Meaning
</td></tr>
<tr>
<td> SN </td><td> Sequence Number
</td></tr>
<tr>
<td> RS </td><td> Resquecer Service
</td></tr>
<tr>
<td> FRS</td><td> Full Resequencer Service
</td></tr>
<tr>
<td> SRS</td><td> Smart Resequencer Service
</td></tr>
<tr>
<td> Q </td><td> the Queue as used in a Message Queue
</td></tr>
<tr>
<td> PR </td><td> processing request, ie to either add or delete a resource and do the needed processing for that. the PR is the combination of JMS message and record.
<p><b>NOTE:</b> it is legal to have &gt;1 PRs for the same recource on the processing chain. this concept's goal is to bring the PRs into proper order and not neccessarily have just one PR per resource in the processing chain.<br />
<b>NOTE:</b> the term "message" is often used interchangably for this, albeit not quite correct.
</p>
</td></tr>
<tr>
<td> PT </td><td> processing target, basically any pipelet that stores some information on the record other than in Bin- or records storage and where the processing order matters. A search index is an example of this.
</td></tr>
<tr>
<td> CA </td><td> Config Annotation. A specially named annotation that is attached to the record holding all needed information the RS needs to do its work.
</td></tr></table>
<a name="Ideas"></a><h4> <span class="mw-headline"> Ideas </span></h4>
<ul><li> replace the SN with a more general ComparableObject
</li></ul>
<!--
NewPP limit report
Preprocessor node count: 77/1000000
Post-expand include size: 2585/2097152 bytes
Template argument size: 1642/2097152 bytes
#ifexist count: 0/100
-->
<!-- Saved in parser cache with key wikidb:pcache:idhash:21687-0!1!0!!en!2!edit=0 and timestamp 20120203101558 -->
<div class="printfooter">
Retrieved from "<a href="ProcessingMessageResequencer.html">http://wiki.eclipse.org/SMILA/Specifications/ProcessingMessageResequencer</a>"</div>
<div id="catlinks"><p class='catlinks'><a href="http://wiki.eclipse.org/Special:Categories" title="Special:Categories">Category</a>: <span dir='ltr'><a href="http://wiki.eclipse.org/Category:SMILA" title="Category:SMILA">SMILA</a></span></p></div> <!-- end content -->
<div class="visualClear"></div>
</div>
</div>
</div>
<!-- Yoink of toolbox for phoenix moved up -->
</div>
</div>
<div id="clearFooter"/>
<div id="footer" >
<ul id="footernav">
<li class="first"><a href="http://www.eclipse.org/">Home</a></li>
<li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
<li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
<li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
<li><a href="http://www.eclipse.org/org/foundation/contact.php">Contact</a></li>
<li><a href="http://wiki.eclipse.org/Eclipsepedia:About" title="Eclipsepedia:About">About Eclipsepedia</a></li>
</ul>
<span id="copyright">Copyright &copy; 2012 The Eclipse Foundation. All Rights Reserved</span>
<p id="footercredit">This page was last modified 12:09, 9 October 2009 by <a href="http://wiki.eclipse.org/User:Tmenzel.brox.de" title="User:Tmenzel.brox.de">thomas menzel</a>. Based on work by <a href="http://wiki.eclipse.org/User:Igor.novakovic.empolis.com" title="User:Igor.novakovic.empolis.com">Igor Novakovic</a>.</p>
<p id="footerviews">This page has been accessed 2,161 times.</p>
</div>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
var pageTracker = _gat._getTracker("UA-910670-4");
pageTracker._trackPageview();
</script>
<!-- <div class="visualClear"></div> -->
<script type="text/javascript">if (window.runOnloadHook) runOnloadHook();</script>
</div>
<!-- Served in 0.133 secs. --></body></html>