Swift没有在Build Options下添加Ob-C桥接头文件的选项(Swift no option to add an Ob-C bridging header file under Build Options)

 看起来您在本地计算机上运行该代码并尝试连接到Google Compute Engine VM; 默认情况下，GCE具有严格的防火墙设置，以避免将外部IP地址暴露给任意入站连接。 如果您使用的是默认值，那么您的Hadoop集群应该位于“默认”GCE网络上。 您需要按照添加防火墙说明来允许端口8020上的传入TCP连接以及其他Hadoop端口上的连接以及本地IP地址以实现此操作。 它看起来像这样： 
 
gcloud compute firewall-rules create allow-http \
    --description "Inbound HDFS." \
    --allow tcp:8020 \
    --format json \
    --source-ranges your.ip.address.here/32
 
 请注意，您确实希望避免打开0.0.0.0/0源范围，因为Hadoop没有对这些传入请求进行身份验证或授权。 您需要尽可能地将其限制为仅计划拨入的入站IP地址。您可能还需要打开其他几个端口，具体取决于您使用哪种功能连接到Hadoop。 
 
 更一般的建议是，只要有可能，您应该尝试在Hadoop集群本身上运行代码; 在这种情况下，您将使用主主机名本身作为HDFS权限而不是外部IP： 
 
hdfs://<master hostname>/foo/bar
 
 这样，您可以将端口暴露限制在仅仅SSH端口22，SSH端口守护程序正确地控制传入流量，然后您的代码不必担心哪些端口是打开的，甚至不必担心处理IP地址所有。 

It looks like you're running that code on your local machine and trying to connect to the Google Compute Engine VM; by default, GCE has strict firewall settings to avoid exposing your external IP addresses to arbitrary inbound connections. If you're using defaults then your Hadoop cluster should be on the "default" GCE network. You'll need to follow the adding a firewall instructions to allow incoming TCP connections on port 8020 and possible on other Hadoop ports as well from your local IP address for this to work. It'll look something like this:
 
gcloud compute firewall-rules create allow-http \
    --description "Inbound HDFS." \
    --allow tcp:8020 \
    --format json \
    --source-ranges your.ip.address.here/32
 
Note that you really want to avoid opening a 0.0.0.0/0 source-range since Hadoop isn't doing authentication or authorization on those incoming requests. You'll want to restrict it as much as possible to only the inbound IP addresses from which you plan to dial in. You may need to open up a couple other ports as well depending on what functionality you use connecting to Hadoop.
 
The more general recommendation is that wherever possible, you should try to run your code on the Hadoop cluster itself; in that case, you'll use the master hostname itself as the HDFS authority rather than external IP:
 
hdfs://<master hostname>/foo/bar
 
That way, you can limit the port exposure to just the SSH port 22, where incoming traffic is properly gated by the SSH daemon, and then your code doesn't have to worry about what ports are open or even about dealing with IP addresses at all.