hub changes for stream/repost with extensions #113
No reviewers
Labels
No labels
area: database
area: documentation
area: elasticsearch
area: herald
area: packaging
area: scribe
consider soon
critical
dependencies
good first issue
hacktoberfest
help wanted
improvement
needs: repro
new feature
priority: blocker
priority: high
priority: low
priority: medium
type: bug
type: bug-fix
type: discussion
type: feature request
type: improvement
type: new feature
type: refactor
type: task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/hub#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "moodyjon/limited_repost"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context: https://github.com/lbryio/lbry-sdk/pull/3706
Not sure that the query for extensions works as well as I would like.
Also I plan to look into some of the options for limiting how many fields, and how deep the indexing of fields within extensions goes:
https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-settings-limit.html
This surprised me, but it appears that the old way of doing this did not handle deletions of extensions. It's like it was applying
doc
as a set of changes to the existing doc.The new way is intended to completely replace the
doc
with new contents.The point of commit https://github.com/lbryio/hub/pull/113/commits/5b1d4bff5c7c57b8613a147fc4d2a89bb9e0d4cb
Is to cut off indexing of all the nested things inside extensions. The fields which are “runtime” can be queried, but not as time-efficiently as others. So you can find extension “cad” quickly because they are indexed, but query on fields like “cad.foo” are evaluated more slowly.
It appears this was not necessary. I must have had some other problem involving the
ALL_FIELDS
orFIELDS
definitions or theprepare_claim_metadata_batch() definition
. Reverted.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.