kiji-rest-client: REST-47. Update README.md to reflect new home.

Updating to reflect the new home of the ruby gem.
commit: https://github.com/kijiproject/kiji-rest-client/commit/7bee26c215213f57804f19c40dc9a6ad3e9a8a24
kiji-express: EXP-207. Make entityId available to lifecycle phases.

issue: https://jira.kiji.org/browse/EXP-207
review: https://review.kiji.org/r/1167
commit: https://github.com/kijiproject/kiji-express/commit/b726dea8b4fdef2e8b4dfac7e7e2c39d01538c2e
kijiproject.github.com: Update docs after release.

commit: https://github.com/kijiproject/kijiproject.github.com/commit/631008a1783ba391e80315c0e632ab9eee0da7fb
kiji-express: EXP-197. Add support for sequence file Input/Output sources in the Modeling Lifecycle.

issue: https://jira.kiji.org/browse/EXP-197
review: https://review.kiji.org/r/1163
commit: https://github.com/kijiproject/kiji-express/commit/22b24c31eb17f4b46c02572bb3b97c58b2c70752
kiji-model-repository: KIJIREPO-33. Fix some bugs in the parsing of the artifact name.

Fix the regular expression that is used to parse the artifact name into a name
and version. Likewise, ensure that the MavenArtifactName will properly split the
name into a group/artifact.

Reviewer: shashir
commit: https://github.com/kijiproject/kiji-model-repository/commit/26cacc60105c3657ed02ad996dc623178448ebf0
kiji-express: EXP-227. Moves TimeRange case classes out of package object.

commit: https://github.com/kijiproject/kiji-express/commit/8fa047da4a735bd3883e3a8586d03ca946d83c40
kiji-model-repository: KIJIREPO-34. Fix broken version of kiji-model-repository module.

issue: https://jira.kiji.org/browse/KIJIREPO-34
review: https://review.kiji.org/r/1184
commit: https://github.com/kijiproject/kiji-model-repository/commit/1baa5834c995a84409685bccbffc6717e4f86464
kijiproject.github.com: DOCS-110, DOCS-112 Two tiny typos in Music Recommendations tutorial

commit: https://github.com/kijiproject/kijiproject.github.com/commit/16bf0901e0042bd0802faa4de8265cf3b136d0bb
kiji-express: EXP-223. Make constructors for generic AvroValues public.

issue: https://jira.kiji.org/browse/EXP-223
review: https://review.kiji.org/r/1173
commit: https://github.com/kijiproject/kiji-express/commit/8b2ea87b6d1c2623c4da364ea5016f2258784165
kiji-express: EXP-219.  Finalize KijiInput API for 1.0 release.

EXP-219.  Finalize KijiInput API for 1.0 release.

Remove explicit KijiInput class so that calls to KijiInput that used to
look like:

  KijiInput(tableURI)("family:column1" -> 'word)

now look like:

  KijiInput(tableURI, "family:column1" -> 'word)

Also updated Scaladoc and all unit tests.

wip

Updated comments and fixed remaining compilation bugs

EXP-219.  Updated style based on feedback from Robert.

Got rid of trailing whitespace, updated Scaladoc to match conventions,
fixed hanging indents, and renamed kijiURI to kijiUri.

EXP-219.  Reverted unnecessary changes to test files.

I had previously made a minor change to a couple of test cases that
weren't compiling.  The problem was some interaction of my IntelliJ and
Maven setups and the order in which I was running Maven commands.
commit: https://github.com/kijiproject/kiji-express/commit/5fdae20e76c67b8c2ff6700ed1f115eb2f940bde
kiji-express: EXP-225. Stop using Configurations as a key to the EntityIdCache

issue: https://jira.kiji.org/browse/EXP-225
review: https://review.kiji.org/r/1178
commit: https://github.com/kijiproject/kiji-express/commit/b942dc5a802faaf32c85234d5b559992f635ae92
kiji-hive-adapter: Remove closing of SchemaTable that was causing regression tests to fail.

Signed-off-by: Christophe Taton <taton@wibidata.com>
commit: https://github.com/kijiproject/kiji-hive-adapter/commit/2b558e0689e56fd484eae00cd0eb6e3c8497ac4a
kiji-express-music: Updates model definition and environment.

Reviewed by: renuka
commit: https://github.com/kijiproject/kiji-express-music/commit/dad54ad4c5f24d6c4b6c79926eaa2a145df4ec6c
kiji-express: EXP-185. Make extractor in ScoreProducer optional

Extractor is now an Option, and default input/output fields
are used if it is not specified.

issue: https://jira.kiji.org/browse/EXP-185
review: https://review.kiji.org/r/1193
commit: https://github.com/kijiproject/kiji-express/commit/a265145bc53f8ffdfbacb22ef20b7650ff5f899d
kiji-express-examples: EXP-220. Improve KijiOutput API

issue: https://jira.kiji.org/browse/EXP-220
review: https://review.kiji.org/r/1202
commit: https://github.com/kijiproject/kiji-express-examples/commit/879d215d5677dae9cc7dcce05cfa268f15133efc
kiji-rest: Service script no longer prints move error.

review: https://review.kiji.org/r/1200/
commit: https://github.com/kijiproject/kiji-rest/commit/ca1dee1d4c52ddffb9239dfd6367b1976dccfc05
kiji-model-repository: KIJIREPO-26. Adds scoring server startup scripts.

review: https://review.kiji.org/r/1192/
commit: https://github.com/kijiproject/kiji-model-repository/commit/399317ad927040a1d657515437dadbff87633873
kiji-express: EXP-220. Improve KijiOutput API

issue: https://jira.kiji.org/browse/EXP-220
review: https://review.kiji.org/r/1187
commit: https://github.com/kijiproject/kiji-express/commit/02c3fe4e0575cddd66e00b63525148af6d267736
kiji-express-music: EXP-220. Improve KijiOutput API

issue: https://jira.kiji.org/browse/EXP-220
review: https://review.kiji.org/r/1203
commit: https://github.com/kijiproject/kiji-express-music/commit/2688b2a17c7031db9fc932330b68c50aa91045fe
kiji-express: EXP-153. Support joins on entity_ids.

Changes the entityId implementations to support joins. EntityIds are created by
users or when reading from a KijiInputSource and all entityIds will have a list
of "components" which are either the formatted entityId components or a single
component reflecting the raw HBase rowkey. The join semantics are as follows:
1) If a user wants to join two pipes ultimately sourced from a KijiInput, this
is okay as long as the components are the same. For hashed keys, this will
compare the hashed keys so there is a theoretical possibility that two rows
could be considered the "same" even though they are different entity_ids that
happened to hash to the same value.
2) If a user wants to join a Kiji table with a data source like a text file,
this is okay because the user can create an entity id from the components (e.g.
EntityId("hello", "world")) and join that with the entity_id coming out of the
Kiji table.
3) If a user wants to join a Kiji table that has a hashed key with a data source
containing the "unhashed" value, the join will fail unless the user does the
hashing to match that of what we stored.

Reviewer: robert
commit: https://github.com/kijiproject/kiji-express/commit/1ccb1849a30978b1a3be110259430969fc8d1699