Databases
StackOverflow2013
Postsdbo
POUsing Scala Actors to create sth like a Pipeline
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Scala Actors to create sth like a Pipeline
    primarykey
    data
    text
    <p>I am struggling with the following problem for a week by now and need some advice.</p> <pre><code>def query(title: String): List[Search] // query("Terminator") =&gt; ["Terminator I", "Terminator II", "Terminator 1984", etc...] def searchIMDB(s: Search): List[SearchResult] def searchTMDB(s: Search): List[SearchResult] def filterRedundantSearchResults(sr: SearchResult): Option[SearchResult] def fetchIMDB(sr: SearchResult): List[MetaInfo] def fetchTMDB(sr: SearchResult): List[MetaInfo] def consolidate(infos: List[MetaInfo]): List[List[MetaInfo]] </code></pre> <p>I want to construct a Pipeline like:</p> <pre><code>query("Terminator") -&gt; [askIMDB, askTMDB, ...] -&gt; filterRedundantSearchResults (already-searched-state per query) -&gt; [fetchIMDB, fetchTMDB, ...] -&gt; consolidate (collected-meta-infos-state per query) =&gt; List[ TerminatorI-List[MetaInfo], TerminatorII-List[MetaInfo], ...] </code></pre> <p>So far, I have implemented every Pipeline-Segment as an Actor. I need to create dedicated actor-instances for every Query, as some of those actors like filterXXX and consolidate need to maintain state per query.</p> <p>Functions like askIMDB produce multiple results which I want to process concurrently (each to a seperate actor). So I have not found any way to pre-construct the whole graph of actors <em>before</em> executing the query() and neither an elegant way to modify it at runtime.</p> <p>My first try was a chain of actors and passing sth like Transaction-IDs in the messages, so each Actor had a Map[TransactionID->State] but this felt rather ugly. The second try was to create a sort-of-Pipeline abstracting the digraph of actors into one flow but I failed so far.</p> <p>This is my first post, sorry if I forgot something or the question is to general/pseudo-coded. Any advice very much appreciated. Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UShotzen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing Scala Actors to create sth like a Pipeline
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUsing Scala Actors to create sth like a Pipeline
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUsing Scala Actors to create sth like a Pipeline
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload