Update QueryContext.java

typo
Add examples of SET setting multiple properties

* Added example to SET and MERGE
* Removed the provisional warning on MERGE
Touch up of naming

An index scan returns all the nodes in an index. This is an operation we still don't have in Cypher.
We have unique index seek and normal index seek.
Merge pull request #2137 from karabijavad/patch-1

Fix typo in QueryContext.java
Updated contributor list.
Merge pull request #2138 from systay/logical-naming

Touch up of naming
Merge pull request #2129 from systay/set-examples

Add examples of SET setting multiple properties
Move cost, cardinality, and solvedPredicates back into LogicalPlan

o Replaces PlanTableEntry with LogicalPlan
o Pulls cost and cardinality estimation code out of planners into logical plans
o Some clean up and test refactoring on the side
Move SemanticTable into LogicalPlanContext and cleanup leaf planners

o Unravels issue around Identifier <-> IdName confusion:
   (1) Might want to replace IdName with Identifier again since we don't have types for the latter
   (2) IdNames can be ambiguous due to name shadowing
Pull LogicalPlanContext out and turn {SimpleLogical|Projection}Planner into objects
Changed the algorithm for picking the best plan

Instead of picking a best plan from all the initial plans, we now pick a best plan per set of covered ids

Also disabled relationship seeks in ronja until we support relationship patterns.
Refactoring to make SimpleLogicalPlanner easier to test
Update README.asciidoc
First stab at taking care of predicates in Ronja

* Adds a Selection logical plan
* Adds a selectionApplicator, which is the class responsible
  for applying predicates when possible
* Makes expandAndJoin and the initialiser use it for each plan that
  is produced
Adds PipeMonitor to the FilterPipe, since it's used from Ronja
Makes sure only locked records are changed

There were an issue in RelationshipCreator where, during upgrading a node
to dense representation, some relationships might be read and marked for
changing before they were locked. This could lead to changes being applied
to stale record data.

This commit also fixes other unrelated issues:
 o Getting node degree for a relationship type that didn't exist would be
   mistakedly interpreted as getting the degree for all relationships for
   that node.
 o BatchInserter#getRelationshipIds/getRelationships didn't regard dense
   node representations and so invalid relationships where returned for
   dense nodes.
Merge pull request #2140 from tinwelint/2.1-dense-upgrade-inconsistencies

Makes sure only locked records are changed
Merge pull request #2143 from boggle/predicate-evaluation

Predicate evaluation in Ronja
Add monitors to all the existing pipes
Faster upgrade.

 o Changes strategy from scanning node store to scanning rel store, leading to much less random access.
   Upgrade now requires a single sequential scan through rel store, plus random access into node store,
   one access for each node.
 o Modifies the scanning strategy to use 4K-aligned scan buffer instead of 33b buffer, improves scan speed
   one order of magnitude.
 o Remaining: Memory usage is still very high, need to investigate performance when RAM runs out.