Issue with fields

#2

Hi @mfoldbjerg,

The support for nested items in field level security is already in our Jira. It’s in the next sprint, so I believe it should be available in a month or so.

#3

Hi @sscarduzio,

Thanks for the prompt reply. That definitely sounds great. Just to be on the safe side. So support will be added for blacklisting up til “index.mapping.depth.limit” depth (default: 20)? Not that any of the documents we’re planning will be that deeply nested, but currently we are around 7 levels deep at most, so support for something like “~item.nested1.nested2.nested3.nested4.*” would be super.

#4

@coutoPL does this sound ok?

#5

Hi @sscarduzio,

Are there any news regarding this feature ? When might it be available ?

Thanks,
Michael

#6

It’s the second task in the line in the current sprint.

#7

Hi @sscarduzio,

Has this feature been released?
If not is there an ETA for when it will be released?

#8

@esmann sorry for the delay on this, but we discovered two security bugs that took priority :frowning_face:

Will try to squeeze this in for next week.

#9

Any news on this? :slight_smile:

#10

@coutoPL do you have an estimate on when we can expect this?

#11

This is next task, so it should be done this month for sure.

#12

Any news with regards to this? - some sort of release outlook would be highly appreciated! We have some impatient external clients whom we cannot service until we have the fix - and we have been putting them off for more than 3 months now…

#13

@AndersBruun, this issue is being currently being worked on.

#14

the improvement is almost ready:

1 Like
#15

@AndersBruun @esmann @mfoldbjerg is any of you available for a pre-release early access to this feature? Would be amazing to have your feedback. Once again, sorry for the delay.

#16

Not a problem - will be glad to try it out

#17

what ES version do you use? I’ll send proper build

#18

version 6.6.2 and 6.8.3 (different clusters)

#19

Any ETA on the builds?

#20

sorry, yesterday we figured out that we have regression bug, so I didn’t want to send you build with the bug. Now it is fixed, so here are the builds:

https://readonlyrest-data.s3-eu-west-1.amazonaws.com/build/1.18.7/readonlyrest-1.18.7_es6.6.2.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA5SJIWBO54AGBERLX/20190926/eu-west-1/s3/aws4_request&X-Amz-Date=20190926T160012Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=9567870da83f075bbcce9688cd4b6e852ed47196ed3aee12daf7108f1317c311

https://readonlyrest-data.s3-eu-west-1.amazonaws.com/build/1.18.7/readonlyrest-1.18.7_es6.8.3.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA5SJIWBO54AGBERLX/20190926/eu-west-1/s3/aws4_request&X-Amz-Date=20190926T160033Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=c11ecd37d9d7a810e5bbc15aec80d8e39bd7cda67942993442ce6be00888971d

#21

We’ve now tested the plugin and at least for our use cases it works as promised, so thanks a lot for the added functionality

1 Like