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

network_flow_restriction query filters out clusters #47

Closed
pies opened this issue Feb 21, 2019 · 4 comments
Closed

network_flow_restriction query filters out clusters #47

pies opened this issue Feb 21, 2019 · 4 comments

Comments

@pies
Copy link

pies commented Feb 21, 2019

await this.queryWithRetry(`

oc.cluster_id IN (SELECT SUBSTR(uic_code, 3, 4) AS nlc FROM location_railcard WHERE railcard_code = 'NEW')

This removes (all?) flows to clusters because location_railcard does not contain (some?) clusters.

@pies pies changed the title network_flow_restriction quyery filters out clusters network_flow_restriction query filters out clusters Feb 21, 2019
@linusnorton
Copy link
Collaborator

I don't think so, I think it extracts the NLC from the cluster ID and uses that as the NLC... but I must admit I'm not 100% on that.

@pies
Copy link
Author

pies commented Feb 22, 2019

Well, we were missing some restrictions, like DFD to RAM, because RAM is present in flows as its clusters and those clusters were not included in location_railcard.

Our implementation removes this restriction and adds SVR and SVS to the list of tickets, which bumps the number of rows significantly (to 400k). It fixes some issues (admittedly not huge ones) and makes it a more general tool for checking whether there's an off-peak on the particular flow. I think it's worth the extra resources, but YMMV obviously.

@linusnorton
Copy link
Collaborator

Yeah, I would like that patch if you have it available

@pies
Copy link
Author

pies commented Mar 28, 2019

#48

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

2 participants