[jira] [Closed] (JAMES-2927) Avoid null value binding in prepared statements

["Benoit Tellier (Jira)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-2927.
---------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

https://github.com/linagora/james-project/pull/2785 solved this

> Avoid null value binding in prepared statements
> -----------------------------------------------
>
>                 Key: JAMES-2927
>                 URL: https://issues.apache.org/jira/browse/JAMES-2927
>             Project: James Server
>          Issue Type: Improvement
>          Components: cassandra
>            Reporter: Benoit Tellier
>            Priority: Major
>             Fix For: 3.5.0
>
>
> A tumbstone is created when a null value is specified in a prepared statement.
> This is due to the fact that null has the meaning `remove` and not the meaning `unspecified`, which is represented by no binding at all.
> Of course unwanted tumbstones occurs with a performance cost.
>     
> The recommended method for fixing this is to separate nullable parts of the statements in other prepared statements, that can logically grouped together without overhead using batch statements.
> Read this for further information: https://thelastpickle.com/blog/2016/09/15/Null-bindings-on-prepared-statements-and-undesired-tombstone-creation.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org