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

How to index deleted points? #41

Open
gmaclennan opened this issue Feb 5, 2017 · 1 comment
Open

How to index deleted points? #41

gmaclennan opened this issue Feb 5, 2017 · 1 comment
Labels

Comments

@gmaclennan
Copy link
Member

Consider the following scenario:

For a point A, one user changes a tag, and another user moves the point, creating a fork. The point is then deleted:

        /--- A1 <---\
A0 <----             ---- A3 (deleted)
        \--- A2 <---/

If we are going to return deleted points, what should be returned from a bbox query?

My thoughts: A3 should be returned whether A1 or A2 is in the bbox. The client should be responsible for choosing what to do next (e.g. read the two linked points A1 and A2 and display them on the map). This would mean that there should be two references in the kdb index both pointing to A3. We would probably need to dedupe for the results of a bbox that included both A1 and A2.

@gmaclennan
Copy link
Member Author

We would also need to consider the following scenario:

        /--- A1 <-----\
A0 <----               ---- A3 (deleted)
        \             /
         \--- A2 <----
                      \---- A4

I think the above solution would work for that too.

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

No branches or pull requests

1 participant