| commit | 4ef74c3aa17bac2b18006ee3144e16eee833fb9c | [log] [tgz] |
|---|---|---|
| author | stephen <spmallette@gmail.com> | Tue Nov 19 13:20:15 2019 -0500 |
| committer | stephen <spmallette@gmail.com> | Tue Dec 03 11:34:19 2019 -0500 |
| tree | 2ccbdb46ea937a240a27a0992717cd1fcdd5adf8 | |
| parent | c102bc3fa82ab99aec2f305046a3640ba867c941 [diff] |
TINKERPOP-2235 Major refactoring and introduction of ScalarMapStep ScalarMapStep extends and replaces MapStep as the "easy" way to implement a new MapStep. ScalarMapStep works nicely when you don't have to fuss with null logic and is still appropriate for use in those cases where a step will not produce a null value (e.g. addV()). For all other cases, you basically have to extend MapStep directly and implement processNextStart() by hand.