You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each spanning relation (thus a span covering a token) there is an entry in the rank table with the edge. This information is never used in the query generation, but when re-constructing the graph.
For continuous spans the graph can be re-constructed without this explicit storage of the edges (using the left/right_token_index). We should remove the unnecessary rank entries on import.
This will reduce the size of the facts table and it's indexes dramatically on corpora that only contain spans.
The text was updated successfully, but these errors were encountered:
For each spanning relation (thus a span covering a token) there is an entry in the rank table with the edge. This information is never used in the query generation, but when re-constructing the graph.
For continuous spans the graph can be re-constructed without this explicit storage of the edges (using the left/right_token_index). We should remove the unnecessary rank entries on import.
This will reduce the size of the facts table and it's indexes dramatically on corpora that only contain spans.
The text was updated successfully, but these errors were encountered: