Re: ${!var} In Scripts

2019-03-04 Thread Allen Wittenauer
> On Mar 4, 2019, at 10:00 AM, Daniel Templeton wrote: > > Do you want to file a JIRA for it, or shall I? Given I haven’t done any Hadoop work in months and months … - To unsubscribe, e-mail:

Re: ${!var} In Scripts

2019-03-04 Thread Daniel Templeton
Do you want to file a JIRA for it, or shall I? Daniel On 3/4/19 9:55 AM, Allen Wittenauer wrote: On Mar 4, 2019, at 9:33 AM, Daniel Templeton wrote: Thanks! That's not even close to what the docs suggest it does--no idea what's up with that. It does. Here’s the paragraph: "If

Re: ${!var} In Scripts

2019-03-04 Thread Allen Wittenauer
> On Mar 4, 2019, at 9:33 AM, Daniel Templeton wrote: > > Thanks! That's not even close to what the docs suggest it does--no idea > what's up with that. It does. Here’s the paragraph: "If the first character of parameter is an exclamation point (!), a level of variable

Re: ${!var} In Scripts

2019-03-04 Thread Daniel Templeton
Thanks!  That's not even close to what the docs suggest it does--no idea what's up with that.  With your example, I was able to figure out exactly what the issue is.  On Ubuntu 18/bash 4.4, dot is rejected in the name of the variable to substitute, which is sane in principle as dots aren't

Re: ${!var} In Scripts

2019-03-01 Thread Allen Wittenauer
> On Mar 1, 2019, at 3:04 PM, Daniel Templeton wrote: > > There are a bunch of uses of the bash syntax, "${!var}", in the Hadoop > scripts. Can anyone explain to me what that syntax was supposed to achieve? #!/usr/bin/env bash j="hi" m="bye" k=j echo ${!k} k=m echo ${!k}