tree e23e64061818819d1d27d6fdc38b9eba07828c38
parent ad028de53842cb7709cd1db04976aa689fc5ad6d
author Gian Merlino <gianmerlino@gmail.com> 1619656109 -0700
committer GitHub <noreply@github.com> 1619656109 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgif2tCRBK7hj4Ov3rIwAAKwgIALDXewRuqoImxaaAX9+CgGJy
 YS+zgzSQop2xpEX6t6fIDAY24iPgXZyiS8jOTwOI5D8Yz2ijza2/EHmsdTPNwvs2
 JsDLg5E/xjCnV7Lv/HDfiQYxlxqMHb8DXwlFYzyTIfUk6C2uFn8yp6U7AkwDmO2L
 VyLnbSPLE/CuoUCoaLVG/X5sOa+7BNIvaaasneQapdONZkg58x+R0IC/qhw9HYCP
 urP8p2wLxdKJY4Wwbs/GWb7hNzLhM4BjKTX+91NWHS2dqfkiDN11dsCLsJbiHrfN
 IYy1gC+5DZ0uUfz0JBmTSscSaxVFMoC2gJX4R0UaJIUvelK3C0YN6K2sz43Fda4=
 =3vv/
 -----END PGP SIGNATURE-----
 

InDimFilter: Fix cache key computation to avoid collisions. (#11168)

The prior code did not include separation between values, and encoded
null ambiguously. This patch fixes both of those issues by encoding
strings as length + value instead of just value.

I think cache key computation was OK prior to #9800. Prior to that
patch, the cache key was computed using CacheKeyBuilder.appendStrings,
which encodes strings as UTF-8 and inserts a separator byte (0xff)
between them that cannot appear in a UTF-8 stream.