You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In CommandLineIngestorDriver whitespace in key and value is not trimmed, while it is trimmed in PropertiesIngestorDriver. E.g. key1 = value1 will be stored as key1 (with whitespace at end) with CommandLineIngestorDriver, but as key1 in PropertiesIngestorDriver. The behavior of PropertiesIngestorDriver is the expected one.
An empty property, i.e. some.key= causes an exception in CommandLineIngestorDriver, but is allowed in PropertiesIngestorDriver. This is inconsistent. Either it should always cause an exception, or it should be allowed. Probably the behavior of PropertiesIngestorDriver should be favoured since it directly uses the behaviour of Configuration2. Users familiar with Configuration2 would find a differing behaviour unexpected.
Fix inconsistencies:
In
CommandLineIngestorDriverwhitespace in key and value is not trimmed, while it is trimmed inPropertiesIngestorDriver. E.g.key1 = value1will be stored askey1(with whitespace at end) withCommandLineIngestorDriver, but askey1inPropertiesIngestorDriver. The behavior ofPropertiesIngestorDriveris the expected one.An empty property, i.e.
some.key=causes an exception inCommandLineIngestorDriver, but is allowed inPropertiesIngestorDriver. This is inconsistent. Either it should always cause an exception, or it should be allowed. Probably the behavior ofPropertiesIngestorDrivershould be favoured since it directly uses the behaviour ofConfiguration2. Users familiar withConfiguration2would find a differing behaviour unexpected.