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

Specification with globbing yields conflict if you set a more specific value on a key #2179

Open
Piankero opened this Issue Aug 12, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@Piankero
Contributor

Piankero commented Aug 12, 2018

Steps to Reproduce the Problem

When setting a metadata with a globbing, eg _ and later on setting a more specific value,
a conflict occurs in the metadata.

sudo su
kdb setmeta /test/_/size check/range 1-100                  
#> Using keyname spec/test/_/

#Create an arbitrary key which matches the glob
kdb set /test/abc/size 90                                       
#> Using name system/test/abc/size
#> Create a new key system/test/abc/size with string "90"

#Set a more specific range
kdb setmeta /test/abc/size check/range 2-99                      
#> Using keyname spec/test/abc/size

#Watch the world burn
kdb lsmeta /test/abc/size                                         
#> check/range
#> conflict/check/range
#> conflict/collision/#0
kdb getmeta /test/abc/size conflict/collision/#0                   
#> check/range
kdb getmeta /test/abc/size conflict/check/range                   
#> 1-100
kdb getmeta /test/abc/size check/range                            
#> 2-99

Expected Result

kdb lsmeta just gives check/range with 2-99 without conflict metadata.

Actual Result

A conflict occurs.

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Aug 12, 2018

Contributor

Thank you for reporting the problem!

@tom-wa Can you configure the spec plugin to handle this differently?

Contributor

markus2330 commented Aug 12, 2018

Thank you for reporting the problem!

@tom-wa Can you configure the spec plugin to handle this differently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment