Type Members

1.  case class CompositionPipe [HeadL <: Identifiable[HeadL], HeadR <: Identifiable[HeadR], InputL <: Identifiable[InputL], InputR <: Identifiable[InputR], Output <: Identifiable[Output], End <: Identifiable[End]](p1: Pipe[HeadL, InputL], composer: PairwiseComposer[InputL, InputR, Output], p2: Pipe[HeadR, InputR], o: Pipe[Output, End]) extends Pipe[Either[HeadL, HeadR], End] with Product with Serializable

   This is a type of pipe that takes two input data stores and combines them into an output data store.

   This is a type of pipe that takes two input data stores and combines them into an output data store.

   HeadL

   The type of the data store at the beginning of the left pipeline.

   HeadR

   The type of the data store at the beginning of the right pipeline.

   InputL

   The type of the data store that's feeding in on the left side.

   InputR

   The type of the data store that's feeding in on the right side.

   Output

   The type of the data store that's the output data store is going to.

   End

   The type of the data store that's at the end of the output pipeline.

   p1

   The pipeline that feeds into the left side of the pipeline.

   composer

   The PairwiseComposer that composes the two data stores.

   p2

   The pipeline that feeds into the right side of the pipeline.

   o

   The pipeline that is being outputted into.

2.  case class JunctionPipe [Head <: Identifiable[Head], Mid <: Identifiable[Mid], End <: Identifiable[End]](p1: Pipe[Head, Mid], p2: PartialPipe[Mid, End]) extends Pipe[Head, End] with Product with Serializable
3.  case class MapperPipe [Head <: Identifiable[Head], Input <: Identifiable[Input], Output <: Identifiable[Output], End <: Identifiable[End]](p1: Pipe[Head, Input], mapper: Mapper[Input, Output], p2: Pipe[Output, End]) extends Pipe[Head, End] with Product with Serializable

   This is created with the call gitID:--Clone()-->clonedMap (and clonedMap:--CommitExtraction()-->commitInfoMap, but we'll focus on the former) within the example.

   This is created with the call gitID:--Clone()-->clonedMap (and clonedMap:--CommitExtraction()-->commitInfoMap, but we'll focus on the former) within the example. In the case of gitID:--Clone()-->clonedMap, this is a pipeline that goes from Data Store gitID, computed by the mapper Clone(), and then goes down into Data Store b to be sent further down the pipeline.

   Head

   The type of the data store that begins the pipeline; bigglue.examples.GitID in this case.

   Input

   The type of the data store that brings in input to this part of the pipeline; bigglue.examples.GitID In the case of gitID:--Clone()-->clonedMap and bigglue.examples.GitRepo for clonedMap:--CommitExtraction()-->commitInfoMap.

   Output

   The type of the data store that brings in output to this part of the pipeline; bigglue.examples.GitRepo for gitID:--Clone()-->clonedMap, and bigglue.examples.GitCommitInfo for clonedMap:--CommitExtraction()-->commitInfoMap

   End

   The type of the data store that shows up at the end of the pipeline; bigglue.examples.GitCommitGroups in this case.

   p1

   An Input Data Pipe; bigglue.pipes.Implicits.DataNode(gitID) in the example. In the case of clonedMap:--CommitExtraction()-->commitInfoMap, it would be the MapperPipe(gitID:--Clone()-->clonedMap)

   mapper

   The computation (Mapper) of which the inputs gets computed by. Clone() in the example.

   p2

   An Output Data Pipe; bigglue.pipes.Implicits.DataNode(clonedMap) in this example. In the case of clonedMap:--CommitExtraction()-->commitInfoMap, it would be bigglue.pipes.Implicits.DataNode(commitInfoMap).

4.  case class ParallelPartialPipes [Input <: Identifiable[Input], LEnd <: Identifiable[LEnd], REnd <: Identifiable[REnd]](p1: PartialPipe[Input, LEnd], p2: PartialPipe[Input, REnd]) extends PartialPipe[Input, Either[LEnd, REnd]] with Product with Serializable
5.  case class PartialComposerPipe [InputL <: Identifiable[InputL], InputR <: Identifiable[InputR], Output <: Identifiable[Output], End <: Identifiable[End]](composer: PairwiseComposer[InputL, InputR, Output], p: Pipe[Output, End]) extends Product with Serializable
6.  case class PartialMapperPipe [Input <: Identifiable[Input], Output <: Identifiable[Output], End <: Identifiable[End]](mapper: Mapper[Input, Output], p: Pipe[Output, End]) extends PartialPipe[Input, End] with Product with Serializable

   This is a pipe that has no input data store, but has a computation and an ending pipeline.

   This is a pipe that has no input data store, but has a computation and an ending pipeline. This is generated with the --> calls in the pipeline. You can run this in the case of ParallelPipes, and created a sequence of pipes, but that's out of scope for this example. Within the example, we just use this as a stepping point before MapperPipe

   Input

   The data type that the computation puts in. bigglue.examples.GitID In the case of Clone()-->clonedMap and bigglue.examples.GitRepo for CommitExtraction()-->commitInfoMap.

   End

   The type of the data store that shows up at the end of the pipeline; bigglue.examples.GitCommitGroups in this case.

7.  abstract class PartialPipe [Input <: Identifiable[Input], End <: Identifiable[End]] extends AnyRef

   This is a pipe that has no input data store, but has a computation and an ending pipeline.

   This is a pipe that has no input data store, but has a computation and an ending pipeline. This is generated with the --> or +-> calls in the pipeline. You can run this in the case of ParallelPipes, and created a sequence of pipes, but that's out of scope for this example. Within the example, we just use this as a stepping point before MapperPipe and ReducerPipe

   Input

   The data type that the computation puts in. bigglue.examples.GitID In the case of Clone()-->clonedMap and bigglue.examples.GitRepo for CommitExtraction()-->commitInfoMap, and bigglue.examples.GitCommitInfo for FindAuthor()+->authorMap.

   End

   The type of the data store that shows up at the end of the pipeline; bigglue.examples.GitCommitGroups in this case.

8.  case class PartialReducerPipe [Input <: Identifiable[Input], Output <: Identifiable[Output], End <: Identifiable[End]](reducer: Reducer[Input, Output], p: Pipe[Output, End]) extends PartialPipe[Input, End] with Product with Serializable

   This is a pipe that has no input data store, but has a computation and an ending pipeline.

   This is a pipe that has no input data store, but has a computation and an ending pipeline. This is generated with the +-> call in the pipeline. You can run this in the case of ParallelPipes, and created a sequence of pipes, but that's out of scope for this example. Within the example, we just use this as a stepping point before MapperPipe and ReducerPipe

   Input

   The data type that the computation puts in. bigglue.examples.GitCommitInfo in the case of FindAuthor()+->authorMap.

   End

   The type of the data store that shows up at the end of the pipeline; bigglue.examples.GitCommitGroups in this case.

9.  abstract class Pipe [Head <: Identifiable[Head], End <: Identifiable[End]] extends AnyRef

   This is the superclass to MapperPipe and ReducerPipe.

   This is the superclass to MapperPipe and ReducerPipe. See either one of those for further details into what the pipelines end up doing.

10.  case class ReducerPipe [Head <: Identifiable[Head], Input <: Identifiable[Input], Output <: Identifiable[Output], End <: Identifiable[End]](p1: Pipe[Head, Input], reducer: Reducer[Input, Output], p2: Pipe[Output, End]) extends Pipe[Head, End] with Product with Serializable

    In the example, this is created with the call commitInfoMap:-+FindAuthor()+->authorMap within the val pipe = gitID:--Clone()-->clonedMap:--CommitExtraction()-->commitInfoMap:-+FindAuthor()+->authorMap line.

    In the example, this is created with the call commitInfoMap:-+FindAuthor()+->authorMap within the val pipe = gitID:--Clone()-->clonedMap:--CommitExtraction()-->commitInfoMap:-+FindAuthor()+->authorMap line. With this example, this is a pipeline that goes from Data Store c, computed by the reducer FindAuthor(), and then goes down into Data Store d to be sent further down the pipeline.

    Head

    The data store type at the very beginning of the pipeline. In the example, it would be bigglue.examples.GitID

    Input

    The type of the Data Store that brings in input to this part of the pipeline. bigglue.examples.GitCommitInfo in this case.

    Output

    The type of the Data Store that this part of the pipeline outputs to. bigglue.examples.GitCommitGroups in this case.

    End

    The type of the data store that shows up at the end of the pipeline; bigglue.examples.GitCommitGroups in this case.

    p1

    The part of the pipeline before the actual reducer section of the pipeline; In the example, it would be the MapperPipe(gitID:--Clone()-->clonedMap:--CommitExtraction()-->commitInfoMap)

    reducer

    The computation (Reducer) on which the inputs get computed by. FindAuthor() in the example.

    p2

    The part of the pipeline after the actual reducer section of the pipeline; In the example, it would be bigglue.pipes.Implicits.DataNode(authorMap)

11.  case class SequencedPartialPipes [Input <: Identifiable[Input], Mid <: Identifiable[Mid], Output <: Identifiable[Output]](pi: PartialPipe[Input, Mid], po: PartialPipe[Mid, Output]) extends PartialPipe[Input, Output] with Product with Serializable
12.  case class St [Data <: Identifiable[Data]](store: DataStore[Data]) extends Pipe[Data, Data] with Product with Serializable