Skip to content
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

Radically reduce data transfer for search results to scores + ref in binary #72

Open
nealeu opened this issue Oct 14, 2011 · 0 comments

Comments

@nealeu
Copy link
Member

nealeu commented Oct 14, 2011

Significant load on client and server will be around serialization of data to/from server.

We need a front end layer that can take a POJO and map the relevant bits into a whirlwind index, and the rest can go somewhere else for storage.

Our own annotations of what fields to index and map at client side would certainly be beneficial. Also, we can get screaming write perf if we remove the possibility of getting a KeyCollisionException by putting unique keys elsewhere. We just go on unique Ref (i.e. our own @id)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant