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

HPCC-12426 Add WUQueryDetails option to list applicable WsEcl Addresses #6617

Merged

Conversation

afishbeck
Copy link
Member

Signed-off-by: Anthony Fishbeck anthony.fishbeck@lexisnexis.com

Signed-off-by: Anthony Fishbeck <anthony.fishbeck@lexisnexis.com>
@hpcc-jirabot
Copy link

Jira updated

@richardkchapman
Copy link
Member

@GordonSmith Please review

@GordonSmith
Copy link
Member

Looks good.

@richardkchapman
Copy link
Member

@jakesmith Please review for dali impact

const char *netAddr = instance.queryProp("@netAddress");
if (!netAddr || !*netAddr)
continue;
if (streq(netAddr, ".") && daliAddress.length())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks odd - if netAddr = "." - then assume EspProcess/Instance is on dali node?

I'm not clear why you need to special case "." here, but if it is in the environment, then it surely means everything i, includes this esp node.
So you should probably use SocketEndpoint to resolve ".".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like that "." is used for a netAddress in the environment at all. Since the ESP running this code may be one with an explicitly configured address, while others have ".", I have to assume "." means the address of the dali. Weird but the safest way I think. If they move dali, they can't use "."... and then I'd be happier anyway.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you're thinking with environment with a mixture of "."'s and explicity netAddresses.. that would be weird..
I'm not sure what it means..

I think a comment at very least is needed, but really I think since "." means my local IP, it it SocketEndpoint(".") does not match your local IP - then I'd be temped to error with a mis-configuration issue.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I'll first think about looking up the computer reference rather than using the netAddress.

@jakesmith
Copy link
Member

I don't have any efficiency concerns, as this is interacting with a cached copy of the environment.

Not something new to this code, but really retrieving information from the Environment should be better supported by the IConstEnvironment interface.

@afishbeck - a few minor comments

Signed-off-by: Anthony Fishbeck <anthony.fishbeck@lexisnexis.com>
@afishbeck
Copy link
Member Author

@jakesmith updated based on review.

@jakesmith
Copy link
Member

Looks good to merge to me.
@richardkchapman

richardkchapman added a commit that referenced this pull request Nov 12, 2014
HPCC-12426 Add WUQueryDetails option to list applicable WsEcl Addresses

Reviewed-By: Jake Smith <jake.smith@lexisnexis.com>
Reviewed-By: Gordon Smith <gordon.smith@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
@richardkchapman richardkchapman merged commit b06e14d into hpcc-systems:candidate-5.0.4 Nov 12, 2014
@afishbeck afishbeck deleted the listQueryWsEclAddresses branch November 20, 2014 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants