Hey guys, It's become apparent from the discussion in the following issue that there are some limitations with making the transactional READ_WRITE_BEHAVIOR global to all graph operations ( https://issues.apache.org/jira/browse/TINKERPOP3-875 )
With gremlin-server as an example this implies that: If you issue graph.tx().onReadWrite(Transaction.READ_WRITE_BEHAVIOR.MANUAL) (as is automatic when you use the sessionOpProcessor) every subsequent request will need to handle transactions manually. I think this also includes other clients that have no idea this operation was performed. The side effect of this is that sessionless requests (StandardOpProcessor) that should be automatically committed, break. Seeing as fixing this would be a breaking change, let's discuss pros and cons and depending on how things go, create another JIRA ticket (the one linked earlier is being used for another issue) Best, Dylan
