This project is mirrored from https://github.com/neo4j/neo4j.git. Pull mirroring updated .
  1. 05 Mar, 2021 2 commits
    • Emma Holmberg Ohlsson's avatar
      Changes behavior for reading deleted nodes lazily in NodeProxyWrappingNodeValue · 906f2ffc
      Emma Holmberg Ohlsson authored
      This is the result of a support case where reading a concurrently
      deleted relationship lazily over bolt would result in an
      IllegalStateException instead of some transient error that could be
      retried. Intended behaviour is to use transient error instead. In the
      process, other irregularities where found.
      
      This aligns the node case with how it is done for relationships.
      Only return empty labels and properties if node was deleted by us
      (if status of ReadAndDeleteTransactionConflictException that we now
      get from labels() and properties() is transient)
      Co-authored-by: default avatarAnton Persson <anton.persson@neotechnology.com>
      906f2ffc
    • Emma Holmberg Ohlsson's avatar
      Changes behavior for reading deleted relationships lazily in RelationshipProxyWrappingValue · b2d3a448
      Emma Holmberg Ohlsson authored
      This is the result of a support case where reading a concurrently
      deleted relationship lazily over bolt would result in an
      IllegalStateException instead of some transient error that could be
      retried. Intended behaviour is to use transient error instead. In the
      process, other irregularities where found.
      
      The data that we would read lazily in RelationshipProxyWrappingValue
      is relationship type and properties. This is done through different
      paths.
      - writeTo( AnyValueWriter writer ) where both properties and type are
        read
      - properties() where properties are read
      - type() where type is read
      
      We want to throw ReadAndDeleteTransactionConflictException which is more
      descriptive and contains information about if exception is transient
      or not, via Status.
      
      Before
      - Could throw NotFoundException or IllegalStateException
        both of which is a result of the relationship being deleted,
        either in this transaction or other concurrent transaction.
      Now
      - Catch those exceptions and throw ReadAndDeleteTransactionConflictException
        with correct status depending on if relationship was deleted by us
        or by other tx.
      
      Before
      - Could throw IllegalStateException caused by deleted relationship, by us or other
      Now
      - Throw ReadAndDeleteTransactionConflictException with correct Status
      
      // In writeTo we can't throw exception if relationship was deleted by
      // us. Instead we keep old behaviour of using EMPTY_MAP instead.
      Before
      - If reading properties would result in NotFoundException we would use
        EMPTY_MAP. This is only the wanted behaviour if relationship was
        deleted by us.
      Now
      - Only use EMPTY_MAP for properties if relationship was deleted by us
        (if status of ReadAndDeleteTransactionConflictException that we now
        get from properties() is transient)
      Co-authored-by: default avatarAnton Persson <anton.persson@neotechnology.com>
      b2d3a448
  2. 04 Mar, 2021 1 commit
  3. 02 Mar, 2021 1 commit
  4. 26 Feb, 2021 1 commit
  5. 24 Feb, 2021 1 commit
  6. 21 Feb, 2021 1 commit
  7. 12 Feb, 2021 2 commits
  8. 10 Feb, 2021 2 commits
  9. 28 Jan, 2021 1 commit
  10. 26 Jan, 2021 2 commits
  11. 22 Jan, 2021 1 commit
  12. 20 Jan, 2021 1 commit
  13. 13 Jan, 2021 2 commits
  14. 08 Jan, 2021 2 commits
  15. 05 Jan, 2021 1 commit
  16. 22 Dec, 2020 1 commit
  17. 21 Dec, 2020 1 commit
  18. 18 Dec, 2020 3 commits
    • Mattias Finné's avatar
      96f2aa5b
    • Mattias Finné's avatar
      Adds verbose option to QuickImport · a2db79a2
      Mattias Finné authored
      a2db79a2
    • Mattias Finné's avatar
      Improvements to importer processor assignment · 5222a43f
      Mattias Finné authored
      There was this overly optimistic calculation of amount of active CPUs
      in DynamicProcessorAssigner where processing steps that had much lower
      average processing time than the slowest would be counted with a factor
      less than one. This would in some cases lead to an over-assignment
      of threads which could lead to OS scheduling problems. This could lead
      to a slowdown of the import as a whole.
      
      Also stops unnecessary removing threads from "too fast" steps if
      there are still threads that are unassigned, this to make things
      a fair amount more stable so that thread counts doesn't jump up and
      down a whole lot once they have been initially assigned.
      Now instead moves thread from one step to another if bottlenecks
      are discovered.
      5222a43f
  19. 17 Dec, 2020 1 commit
  20. 16 Dec, 2020 1 commit
  21. 15 Dec, 2020 1 commit
  22. 06 Dec, 2020 1 commit
    • Love Kristofer Leifland's avatar
      Move Cypher Shell () · fb9e1cf8
      Love Kristofer Leifland authored
      Squashed 'public/community/cypher-shell/' content from commit 2b24a37dd5d
      
      git-subtree-dir: public/community/cypher-shell
      git-subtree-split: 2b24a37dd5da64bd4f478ad6eb44e93cc843a675
      fb9e1cf8
  23. 03 Dec, 2020 1 commit
  24. 30 Nov, 2020 1 commit
  25. 25 Nov, 2020 1 commit
  26. 23 Nov, 2020 4 commits
  27. 19 Nov, 2020 1 commit
  28. 17 Nov, 2020 1 commit
  29. 16 Nov, 2020 1 commit