19
3
4
Events
Doe geen extra api calls voor next available.
Is nodig voor als mensen dingen willen doen zonder dat ze alles mogen zien.
Doe geen extra api calls voor next available.
Thank you!
Do use api for some things, but use FlexForm system user.
Doe geen extra api calls voor next available.
Is nodig voor als mensen dingen willen doen zonder dat ze alles mogen zien.
wgevaert delete tag 1.6.0
wgevaert create tag 1.6.0
wgevaert create tag v1.7.1
Remove superfluous ContentAnnotator::__construct, add missing import and missing argument to getReplyAnnotators (#6)
Co-authored-by: Wout Gevaert wout@wikibase.nl
Remove superfluous ContentAnnotator::__construct, add missing import and missing argument to getReplyAnnotators (#6)
Co-authored-by: Wout Gevaert wout@wikibase.nl
Fixes for previous pull request.
Remove superfluous ContentAnnotator::__construct, add missing import and missing argument to getReplyAnnotators
Fixes for previous pull request.
Remove superfluous ContentAnnotator::__construct, add missing import and missing argument to getReplyAnnotators
Merge pull request #5 from wgevaert/master
Add Owner information of topics also to replies.
Update extension.json
Remove superfluous ContentAnnotator::__construct, add missing import and missing argument to getReplyAnnotators
Add new annotators to AnnotatorStore
Add new annotators to AnnotatorStore
Add Owner information of topics also to replies.
Requested by rkoopmans
Add Owner information of topics also to replies.
wgevaert delete tag 1.6.0
wgevaert create tag v1.6.0
wgevaert create tag 1.6.0
Change datatype of OwnerNamespaceAnnotation to _keyw from _num (#4)
Namespace number are not numbers in the sense that operations like < or > or + or - or * make sense.
Also see https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html (jan 2022) which states Not all numeric data should be mapped as a numeric field data type. Elasticsearch optimizes numeric fields, such as integer or long, for range queries. However, keyword fields are better for term and other term-level queries.
Authored-by: wgevaert wout@wikibase.nl
Change datatype of OwnerNamespaceAnnotation to _keyw from _num (#4)
Namespace number are not numbers in the sense that operations like < or > or + or - or * make sense.
Also see https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html (jan 2022) which states Not all numeric data should be mapped as a numeric field data type. Elasticsearch optimizes numeric fields, such as integer or long, for range queries. However, keyword fields are better for term and other term-level queries.
Authored-by: wgevaert wout@wikibase.nl
Change datatype of OwnerNamespaceAnnotation to _keyw from _num
Namespace number are not numbers in the sense that operations like < or > or + or - or * make sense.
Also see https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html (jan 2022) which states:
Not all numeric data should be mapped as a numeric field data type. Elasticsearch optimizes numeric fields, such as integer or long, for range queries. However, keyword fields are better for term and other term-level queries.
Set KeywordValue as propertyObjectValue and increase version number
Change datatype of OwnerNamespaceAnnotation to _keyw from _num
Namespace number are not numbers in the sense that operations like < or > or + or - or * make sense.
Also see https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html (jan 2022) which states:
Not all numeric data should be mapped as a numeric field data type. Elasticsearch optimizes numeric fields, such as integer or long, for range queries. However, keyword fields are better for term and other term-level queries.
Change datatype of OwnerNamespaceAnnotation to _keyw from _num
Namespace number are not numbers in the sense that operations like < or > or + or - or * make sense.
Also see https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html (jan 2022) which states Not all numeric data should be mapped as a numeric field data type. Elasticsearch optimizes numeric fields, such as integer or long, for range queries. However, keyword fields are better for term and other term-level queries.
