-
Notifications
You must be signed in to change notification settings - Fork 12
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
Indexed Entities #24
Open
tristantarrant
wants to merge
1
commit into
main
Choose a base branch
from
indexed-entities
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+59
−0
Open
Indexed Entities #24
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
== Indexed entities | ||
|
||
Defining indexed entities in a cache configuration currently requires those entities to be present in the schema cache. For example: | ||
|
||
[source,xml] | ||
---- | ||
<distributed-cache name="cache"> | ||
<indexing> | ||
<indexed-entities> | ||
<indexed-entity>entity.proto</indexed-entity> | ||
</indexed-entities> | ||
</indexing> | ||
</distributed-cache> | ||
---- | ||
requires the `entity.proto` entry. | ||
|
||
Adding entity schemas to the schema cache, however, can only be performed dynamically at runtime and not statically at startup. | ||
|
||
We should allow static configuration of the schema, either directly in the configuration as character data, or by referencing an external resource: | ||
|
||
[source,xml] | ||
---- | ||
<distributed-cache name="cache"> | ||
<indexing> | ||
<indexed-entities> | ||
<indexed-entity>entity.proto</indexed-entity> | ||
<indexed-entity-resource path="another.proto"/> | ||
<indexed-entity-schema name=""><![CDATA[ | ||
package entity; | ||
|
||
/** | ||
* @Indexed | ||
*/ | ||
message Person { | ||
|
||
/** | ||
* @Field(store = Store.YES) | ||
*/ | ||
optional int32 id = 1; | ||
|
||
/** | ||
* @Field(store = Store.YES) | ||
* @SortableField | ||
*/ | ||
required string name = 2; | ||
|
||
/** | ||
* @Field(store = Store.YES) | ||
*/ | ||
required string surname = 3; | ||
} | ||
]]></indexed-entity-schema> | ||
</indexed-entities> | ||
</indexing> | ||
</distributed-cache> | ||
---- | ||
|
||
On cache startup, the cache manager will ensure that the schema is added to the schema cache unless it is already present. | ||
It is up to the user to ensure that external resources are identical across all nodes in the cluster. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about schema updates, since the protobuf schema cache is persistent?