zillabyte 0.9.32 → 0.9.33

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    ZDkwMGU0YTVhOTQxNDlhZGIzMThiMzkzYjk2MmNhNDY0MWQ3YjkwNQ==
+    YjU5NTNkMWYyM2NmMzcyZWI3NmQ5NTE1YzRkZDEzNzBiNzZiZjZiOQ==
   data.tar.gz: !binary |-
-    M2Y2MzljODU4OGYzNjEzOGVhMjZlOTgwNzk3MmVmN2FjMmJmZjQ0ZA==
+    YzQ4Y2E0Y2Y0NGMzNWNkNWZkMDdmMDRhZTdlMmVjZTNjOGY1MjRiYg==
 SHA512:
   metadata.gz: !binary |-
-    MGFjNTNkMjI2Y2U2ZTdlZjU1ODkzNzY3MDQ1OTNhYzUyYTM2ZDVlNDEzZjA5
-    ZDQ5YmU0YWJkMzRkNTBlOTVkYWRlODQwYjlkYzhhOWI1NjkwNWRiZjgyZjNh
-    N2Q2Yjc4MmUxNzRmMjg0ZjQxMGVlY2E5NTJhYzIzMGY5ZjI5NzY=
+    OGEzYzUwMDViMWFkMDc1NmM2M2RiYTZmNjg2YWM4ZTQ3MjY3NmZiMmQ3ZDM3
+    OWI2NmMzNDI4NDA4YzA0NjUxMjQ1ZTI5Zjc5ZTgyNDA2NjdkODVhYjE3MTNm
+    ZWUyZGNiOGE2N2JlOTRiMGEyZDBjNjQzNWIzNGJiZTY1OTA3OWM=
   data.tar.gz: !binary |-
-    ZDMxMDA5YjM1MTJkZmJkZWU3ZjJlNjM1MGIzNjk3M2JkMzM1MGEwOTk3NTZh
-    NjQ0M2E1YzljNWNjNGM3YWU0OGM3MTZmYjNiMjE5YmY0MWU0ZTFlOTQ0MzRm
-    NzVkODc5ZDViNWM0YmQ1ZjQyZmE4YzAxNzllZTBlYjg0NGIwNjQ=
+    ZjlkMDk1YTk5MTU0Y2UyYWIzOGJmMGVhZDMyNGZiN2M4NjY5Mjk4ZTllODE3
+    YTg3MmQ0NzY1ZjRiNDA1YjVhMWU1NTdlN2QyMjg5MmMyOTZjZjNkYzFiOTlm
+    ZjJlODdkYTQ3MzEzZDc0ZWMzZWNhMDJmOTcyNGU5ZWIyYjEyODM=

data/ruby/lib/zillabyte/harness/component_input.rb

@@ -1,19 +1,19 @@
 # OPERATION Component Input 
 # TAGLINE 
 # Declare the input of a component
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # Components work by declaring a “schema” of their inputs and outputs. 
 # The inputs are the expected fields they will look for within incoming tuples. 
 # In an example case, our component declares an input stream named “urls”, and will look for the “url” field of any incoming tuples.
 # 
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #   component.inputs do
 #     name "input_stream_name"
 #     field "field_1", :type_1
 #     field "field_2", :type_2
 #   end
 # 
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 #  "Inputs" stream "name" must be specified as a non-empty STRING with only alphanumeric and underscore characters!
 #  
 #  Field names must be non-empty STRINGS with only alphanumeric or underscore characters.
@@ -22,7 +22,7 @@
 #  
 #  Field types must be SYMBOLS. The following types are allowed :string, :integer, :float, :double, :boolean, :array and :map.
 # 
-# EXAMPLE 
+# RUBY_EXAMPLE 
 # require 'zillabyte'
 #  
 # comp = Zillabyte.component("ruby_component")

data/ruby/lib/zillabyte/harness/component_output.rb

@@ -1,16 +1,16 @@
 # OPERATION Component Output
 # TAGLINE 
 # Declare the output of a component
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # In a similar manner to component inputs, we declare the component output schema for the component. 
 # This determines the output of the component for other Zillabyte functions to expect. This is just like a sink in apps.
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #   component_stream.outputs do
 #     name "output_stream_name"
 #     field "field_1", :type_1
 #     field "field_2", :type_2
 #   end
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 # "Outputs" stream "name" must be specified as a non-empty STRING with only alphanumeric and underscore characters!
 #  
 # Field names must be non-empty STRINGS with only alphanumeric or underscore characters.
@@ -18,7 +18,7 @@
 # Field names cannot be "v[number]", "id", "confidence", "since" or "source" which are reserved Zillabyte names.
 #  
 # Field types must be SYMBOLS. The following types are allowed :string, :integer, :float, :double, :boolean, :array and :map.
-# EXAMPLE 
+# RUBY_EXAMPLE 
 # stream.outputs do
 #   name "plural"
 #   field "word", :string

data/ruby/lib/zillabyte/harness/each.rb

@@ -1,13 +1,13 @@
 # OPERATION Each
 # TAGLINE 
 # The each block can be thought of as a map operation that runs across multiple machines. 
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # The `each` operation is the simplest operation within Zillabyte. It is analogous to the inner
 # block of a conventional "for" loop which is used to apply the same set of manipulations to
 # each record. Similarly, Zillabyte applies the same code logic specified in the each to each 
 # tuple the operation receives.
 #  
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 # # Simplified syntax:
 #  
 #   stream.each do |tuple|
@@ -23,20 +23,22 @@
 #     execute |=block=|
 #   end
 #  
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 # The simplified syntax can be used if a prepare block and other customizations are not needed.
 # 
 #   * **Note:** this syntax only works for a single output stream.
 #  
 # The allowed output formats are :replace and :merge.
+#
 #   * **:replace** : discards the input tuple values and only emits the specified values. This is the default.
 #   * **:merge** : re-emits the input tuple values along with the specified values.
 #  
 # The "prepare" and "execute" blocks can be in do...end format or {} format.
+#
 #   * **"prepare"** block : where any setup is done to prepare for tuple processing in the "execute" block.
 #   * **"execute"** block : where the tuples are actually processed. It must take in a single argument (the "tuple").
 # 
-# EXAMPLE 
+# RUBY_EXAMPLE 
 #  
 # # This is a simple example which emits the url of a tuple 
 # s = s.each do |tuple|

data/ruby/lib/zillabyte/harness/filter.rb

@@ -1,11 +1,11 @@
 # OPERATION Filter
 # TAGLINE 
 # The filter is a conditional each. 
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # Conditional expressions can be used to determine if a
 # tuple received by the operation is emitted.
 #  
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #  # Simplified syntax:
 #     stream.filter do |tuple|
 #       |=block=|
@@ -19,16 +19,17 @@
 #       keep |=block=|
 #     end
 #  
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 # The simplified syntax can be used if a prepare block and other customizations are not needed.
 # 
 #   * **Note:** this syntax only works for a single output stream.
 # 
 # The "prepare" and "keep" blocks can be in do...end format or {} format.
+# 
 #  * **"prepare"** block : where any setup is done to prepare for tuple processing in the "keep" block.
 #  * **"keep"** block : tuples pass through the filter if "keep" returns "True". It must take in a single argument (the "tuple").
 # 
-# EXAMPLE 
+# RUBY_EXAMPLE 
 # # Filter for simple string inclusion
 # stream = stream.filter { |tuple| tuple["url"].include? "hello world" } 
 # 

data/ruby/lib/zillabyte/harness/group_by.rb

@@ -1,9 +1,10 @@
 # OPERATION Group By 
+# TAGLINE
 # Group tuples by keys
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # The `group_by` operation can be used to implement aggregation-type functions
 # such as counting and summing.
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #   stream.group_by do
 #     name "name"                           # optional
 #     group_by "field_1", "field_2", ...
@@ -12,13 +13,15 @@
 #     aggregate |=block=|
 #     end_group |=block=|
 #   end
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 #  
 # The "begin_group", "aggregate" and "end_group" blocks can be in do...end format or {} format.
+# 
 #   * **"begin_group"** block : where the initial values for the aggregation are set. It must take in a single argument (the "grouping tuple", which is emitted at the beginning of each group and contains the values of the fields specified in "group_by").
 #   * **"aggregate"** block : where the aggregation is performed. It must take in a single argument (the "tuple").
 #   * **"end_group"** block : where the final aggregated value is emitted.
-# EXAMPLE 
+#
+# RUBY_EXAMPLE 
 # # Declare the group_by, grouping on the :word field
 # stream = stream.group_by(:word) do
 # 

data/ruby/lib/zillabyte/harness/injected_component.rb

@@ -1,12 +1,12 @@
 # OPERATION Call Component 
 # TAGLINE 
 # Call a component
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # Components can be embedded into other components or even applications. 
 # When running an application that has an embedded component, that component is 
 # joined into the same execution environment as its parent, allowing for high throughput component execution.
 # To embed a component, use the "call_component" operation
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #   stream.call_component do
 #     component_id "component_id"
 #     name "name"                                           # optional
@@ -14,21 +14,23 @@
 #     outputs "output_stream_name_1", ...
 #     output_format :replace OR :merge                      # optional, defaults to :replace
 #   end 
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 # The "component_id" MUST be given and correspond to the name or id listed in the output of "zillabyte components".
 #  
 # The allowed output formats are :replace and :merge. Note that only linear components, i.e. those with only "each" and "filter" operations support :merge.
+# 
 #   * **:replace** : discards the input tuple values and only emits the output values. This is the default.
 #   * **:merge** : re-emits the input tuple values along with the output values.
 #  
 # To correctly stich in the component, the implicit assumptions below WILL BE USED:
+# 
 #   * The "stream" that "call_component" is invoked on MUST correspond to the first listed input stream to the component.
 #   * The streams specified in "additional_inputs" MUST correspond to the other listed input streams in order.
 #   * Tuples emitted from the preceeding operation MUST contain the fields listed for the corresponding component input streams.
 #   * The streams specified in "outputs" must correspond to the listed output streams to the component in order.
 #   * The number of input and output streams specified must match the number listed for the component.
 #  
-# EXAMPLE 
+# RUBY_EXAMPLE 
 # require 'zillabyte'
 # app = Zillabyte.app("plural_app")
 #  

data/ruby/lib/zillabyte/harness/join.rb

@@ -1,13 +1,14 @@
 # OPERATION Join 
+# TAGLINE
 # Join streams together 
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # Joins allow you to combine two streams into one in a manner similar
 # to traditional relational systems. Realtime tuple data from a variety
 # of sources can be combined into a single stream via joins on specified
 # fields. 
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #   lhs_stream.join_with( rhs_stream_object, options )
-# SYNTAX_NOTES  
+# RUBY_NOTES  
 # Options should be specified as a hash. The following keys are recognized:
 #  
 # Mandatory:
@@ -15,9 +16,11 @@
 #  * **"on"** : specifies the fields to join on. The value must be a STRING or a length-2 ARRAY. If value = a STRING, the LH and RH join fields will both be set to this STRING. If value = a length-2 ARRAY, the LH join field will be set to array[0] and the RH join field will be set to array[1].
 # 
 # Optional:
+# 
 #  * **"type"** : specifies the join type. The default is :left. Options are [:inner, :outer, :left, :right]
 #  * **"emits"** : specifies the stream to emit. A "join" may only emit a single stream.
-# EXAMPLE 
+#
+# RUBY_EXAMPLE 
 #  
 # # Left join on a shared field, in this case, an :owner_id
 # joined_stream = auto_stream.join_with(repairs_stream, :on => :owner_id)

data/ruby/lib/zillabyte/harness/sink.rb

@@ -1,17 +1,17 @@
 # OPERATION Sink 
 # TAGLINE 
 # The `sink` is a passive operation that defines the schema of the rows that need to be saved. 
-# HIGH_LEVEL_DESCRIPTION 
+# DESCRIPTION 
 # The `sink` marks the end of a stream. It saves the data it receives according to the schema defined within it.
 #  
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 #   stream.sink do
 #     name "name_of_relation"
 #     column "field_1", :type_1
 #     column "field_2", :type_2 ...
 #   end
 #  
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 # "Sink" relation "name" must be specified as a non-empty STRING with only alphanumeric and underscore characters!
 #  
 # Field names must be non-empty STRINGS with only alphanumeric or underscore characters.
@@ -20,7 +20,8 @@
 #  
 # Field types must be SYMBOLS. The following types are allowed :string, :integer, :float, :double, :boolean, :array and :map.
 #  
-# EXAMPLE 
+# RUBY_EXAMPLE 
+#
 # stream.sink{
 #     name "patent_sink"
 #     column "doc_number", :integer

data/ruby/lib/zillabyte/harness/source.rb

@@ -3,7 +3,7 @@
 # A source is where the data for your app originates and is defined
 # on the app object. 
 # 
-# HIGH_LEVEL_DESCRIPTION  
+# DESCRIPTION  
 # 
 # ## Sourcing From Datasets
 # The easiest way to stream data into a Zillabyte
@@ -20,7 +20,7 @@
 # and specifying any preparatory steps such as initializing global
 # values in the begin_cycle block.
 # 
-# LANGUAGE_SYNTAX 
+# RUBY_SYNTAX 
 # #Sourcing from a dataset:
 #   app.source("dataset_name") # fetch a dataset from Zillabyte
 # 
@@ -32,16 +32,19 @@
 #     begin_cycle |=block=|                       # optional if no initialization needed
 #     next_tuple |=block=|                        # The code to execute on each tuple fetch
 #   end
-# SYNTAX_NOTES 
+# RUBY_NOTES 
 # 
 # The "end_cycle_policy" is used to specify when a cycle should end. Two options are available:
+#
 #   * **:null_emit** : end the cycle when a field contains "nil" or when nothing is emitted from the "next_tuple" block.
 #   * **:explicit** : the end of a cycle is explicitly declared in the "next_tuple" block. This is done by including the "end_cycle" keyword in the "next_tuple" block, e.g. end_cycle if @queue.nil?.
 # 
 # The "begin_cycle" and "next_tuple" blocks can be in do...end format or {} format.
+#
 #   * **"begin_cycle"** block : where any setup is done to initialize the content and quantity of tuples emitted by the "next_tuple" block.
 #   * **"next_tuple"** block : where the tuples are actually emitted.
-# EXAMPLE 
+##
+# RUBY_EXAMPLE 
 #  
 # # Source from the "homepages" relation
 # stream = app.source("homepages")

data/ruby/lib/zillabyte/version.rb

@@ -1,3 +1,3 @@
 module Zillabyte
-  VERSION = "0.9.32" unless defined?(VERSION)
+  VERSION = "0.9.33" unless defined?(VERSION)
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zillabyte
 version: !ruby/object:Gem::Version
-  version: 0.9.32
+  version: 0.9.33
 platform: ruby
 authors:
 - zillabyte
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-11-15 00:00:00.000000000 Z
+date: 2014-11-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -30,14 +30,14 @@ dependencies:
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 0.9.32
+        version: 0.9.33
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 0.9.32
+        version: 0.9.33
 description: The Official Zillabyte Gem
 email:
 - gem@zillabyte.com
@@ -92,7 +92,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.2
+rubygems_version: 2.2.2
 signing_key: 
 specification_version: 4
 summary: The Official Zillabyte Gem