Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kdb import broken in spec namespace #2460

kodebach opened this Issue Mar 6, 2019 · 1 comment


None yet
2 participants
Copy link

kodebach commented Mar 6, 2019

Steps to Reproduce the Problem

echo -e "[test]\n default = value" | kdb import spec/tests/import ni

echo -e "[test]\n default = value" | kdb import spec/tests/import ni

Expected Result

The second line doesn't change anything about the KDB (except file timestamp, etc.)

Actual Result

Something inside of kdb import (most likely the spec plugin, as this only occurs with the spec namespace) butchers the key name and the following error is shown:

The command bin/kdb import terminated unsuccessfully with the info:
the supplied key spec/tests/importt is not below the old parent spec/tests/import
Please report the issue at

Note: spec/tests/import/test somehow became spec/tests/importt.

Further Information

  • kdb import -v doesn't provide any additional information.
  • The parent key or added keys don't matter as long as the spec namespace is used.
  • It is always the / and the first 3 characters after the parent key name that go missing.

This comment has been minimized.

Copy link

markus2330 commented Mar 7, 2019

Thank you for reporting this problem!

@markus2330 markus2330 added the bug label Mar 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.