blocks|key|21407|text|因为(Bourne)+shell变量不能包含点，所以可以用下划线替换它们。每一行都读一遍，翻译一下。在关键字_和评估中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|21408|#/bin/sh

file="./app.properties"

if+[+-f+"$file"+]
then
++echo+"$file+found."

++while+IFS='='+read+-r+key+value
++do
++++key=$(echo+$key+%7C+tr+'.'+'_')
++++eval+${key}=\${value}
++done+<+"$file"

++echo+"User+Id+++++++=+"+${db_uat_user}
++echo+"user+password+=+"+${db_uat_passwd}
else
++echo+"$file+not+found."
fi|code-block|syntax|javascript|21409|请注意，以上内容仅用于翻译。对于_，如果你有一个更复杂的格式，你可能想要使用额外的翻译。我最近不得不解析一个包含许多讨厌字符的完整Ant属性文件，在那里我不得不使用：|21410|key=$(echo+$key+%7C+tr+.-/+_+%7C+tr+-cd+'A-Za-z0-9_')|21411|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

As (Bourne) shell variables cannot contain dots you can replace them by underscores. Read every line, translate . in the key to _ and evaluate.

<pre><code>#/bin/sh

file="./app.properties"

if [ -f "$file" ]
then
 echo "$file found."

 while IFS='=' read -r key value
 do
 key=$(echo $key | tr '.' '_')
 eval ${key}=\${value}
 done &lt; "$file"

 echo "User Id = " ${db_uat_user}
 echo "user password = " ${db_uat_passwd}
else
 echo "$file not found."
fi
</code></pre>

Note that the above only translates . to _, if you have a more complex format you may want to use additional translations. I recently had to parse a full Ant properties file with lots of nasty characters, and there I had to use:

<pre><code>key=$(echo $key | tr .-/ _ | tr -cd 'A-Za-z0-9_')
</code></pre>

blocks|key|21470|text|@fork2x|type|unstyled|depth|inlineStyleRanges|entityRanges|data|21471|我已经尝试过这样的.Please评论，并更新我，无论它是不是正确的方法。|21472|#/bin/sh
function+pause(){
+++read+-p+"$*"
}

file="./apptest.properties"


if+[+-f+"$file"+]
then
++++echo+"$file+found."

dbUser=`sed+'/%5E\#/d'+$file+%7C+grep+'db.uat.user'++%7C+tail+-n+1+%7C+cut+-d+"="+-f2-+%7C+sed+'s/%5E[[:space:]]*//;s/[[:space:]]*$//'`
dbPass=`sed+'/%5E\#/d'+$file+%7C+grep+'db.uat.passwd'++%7C+tail+-n+1+%7C+cut+-d+"="+-f2-+%7C+sed+'s/%5E[[:space:]]*//;s/[[:space:]]*$//'`

echo+database+user+=+$dbUser
echo+database+pass+=+$dbPass

else
++++echo+"$file+not+found."
fi|code-block|syntax|javascript|21473|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

@fork2x

I have tried like this .Please review and update me whether it is right approach or not. 

<pre><code>#/bin/sh
function pause(){
 read -p "$*"
}

file="./apptest.properties"


if [ -f "$file" ]
then
 echo "$file found."

dbUser=`sed '/^\#/d' $file | grep 'db.uat.user' | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`
dbPass=`sed '/^\#/d' $file | grep 'db.uat.passwd' | tail -n 1 | cut -d "=" -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'`

echo database user = $dbUser
echo database pass = $dbPass

else
 echo "$file not found."
fi
</code></pre>

blocks|key|21585|text|我发现使用while+IFS='='+read+-r有点慢(我不知道为什么，也许有人可以在评论中简短地解释一下，或者指向一个这样的答案？)我还发现@Nicolai+answer作为一行程序非常简洁，但效率非常低，因为它会一遍又一遍地扫描整个属性文件，以获取prop的每一个调用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|21586|我找到了一个解决方案，它回答了这个问题，执行得很好，而且它是一行(虽然有点冗长)。|21587|该解决方案进行寻源，但在寻源之前对内容进行了修改：|21588|#!/usr/bin/env+bash

source+<(grep+-v+'%5E+*#'+./app.properties+%7C+grep+'[%5E+]+*='+%7C+awk+'{split($0,a,"=");+print+gensub(/\./,+"_",+"g",+a[1])+"="+a[2]}')

echo+$db_uat_user|code-block|syntax|javascript|21589|解释：|21590|grep+-v+'%5E+*#'：丢弃注释行grep+'[%5E+]+*='：丢弃没有=的行split($0,a,"=")：在=处拆分行并存储到数组a中，即a1是关键字，a2是值gensub(/\./,+"_",+"g",+a[1])：将.替换为_+print+gensub...+"="+a[2]}将上面gensub的结果与=和value连接起来。|21591|编辑:正如其他人指出的，存在一些不兼容问题(awk)，而且它不会验证内容以查看属性文件的每一行是否真的是kv对。但这里的目标是展示既快速又干净的解决方案的总体思路。采购似乎是可行的方法，因为它只需加载一次可多次使用的属性。|21592|entityMap^0|5|L|3K|4|0|0|0|0|0|0|E|K|E|13|1|16|F|1N|1|1Y|1|2D|S|37|1|3B|1|3D|P|45|6|4F|1|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|13|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1U|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|V|$]]

I found using <code>while IFS='=' read -r</code> to be a bit slow (I don't know why, maybe someone could briefly explain in a comment or point to a SO answer?). I also found @Nicolai answer very neat as a one-liner, but very inefficient as it will scan the entire properties file over and over again for every single call of <code>prop</code>.

I found a solution that answers the question, performs well and it is a one-liner (bit verbose line though).

The solution does sourcing but massages the contents before sourcing:

<pre><code>#!/usr/bin/env bash

source &lt;(grep -v '^ *#' ./app.properties | grep '[^ ] *=' | awk '{split($0,a,"="); print gensub(/\./, "_", "g", a[1]) "=" a[2]}')

echo $db_uat_user
</code></pre>

Explanation:

<code>grep -v '^ *#'</code>: discard comment lines
<code>grep '[^ ] *='</code>: discards lines without <code>=</code>
<code>split($0,a,"=")</code>: splits line at <code>=</code> and stores into array <code>a</code>, i.e. a[1] is the key, a[2] is the value
<code>gensub(/\./, "_", "g", a[1])</code>: replaces <code>.</code> with <code>_</code>
<code>print gensub... "=" a[2]}</code> concatenates the result of <code>gensub</code> above with <code>=</code> and value.

Edit: As others pointed out, there are some incompatibilities issues (awk) and also it does not validate the contents to see if every line of the property file is actually a kv pair. But the goal here is to show the general idea for a solution that is both fast and clean. Sourcing seems to be the way to go as it loads the properties once that can be used multiple times.

I am trying to read a properties file from a shell script which contains a period (.) character like below:

<pre><code># app.properties
db.uat.user=saple user
db.uat.passwd=secret


#/bin/sh
function pause(){
 read -p "$*"
}

file="./app.properties"

if [ -f "$file" ]
then
 echo "$file found."
 . $file

echo "User Id " $db.uat.user
echo "user password =" $db.uat.passwd
else
 echo "$file not found."
fi
</code></pre>

I have tried to parse the file after sourcing the file but it is not working since the keys contains the "." character and there are spaces in that value also.

My properties file always resides in the same directory of the script or somewhere in /usr/share/doc

How to read a .properties file which contains keys that have a period character using Shell script

我正在尝试从包含句点(.)的shell脚本读取属性文件。字符如下：# app.propertiesdb.uat.user=saple userdb.uat.passwd=secret#/bin/shfunction pause(){   read -p "$*"}file="./app.properties"if [ ...

问如何使用Shell脚本读取包含句点字符的键的.properties文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Shell脚本读取包含句点字符的键的.properties文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Shell脚本读取包含句点字符的键的.properties文件
EN