在大数据的当下，各种spark和hadoop的框架层出不穷。各种高端的计算框架，分布式任务如乱花般迷眼。你是否有这种困惑！——有了许多的分布式任务，但是每天需要固定时间跑任务，自己写个调度，既不稳定，又没有可靠的通知。

想要了解Oozie的基础知识，可以参考这里

那么你应该是在找——Oozie。

Oozie是一款支持分布式任务调度的开源框架，它支持很多的分布式任务，比如map reduce,spark,sqoop,pig甚至shell等等。你可以以各种方式调度它们，把它们组成工作流。每个工作流节点可以串行也可以并行执行。

如果你定义好了一系列的任务，就可以开启工作流，设置一个coordinator调度器进行定时的调度了。

有了这些工作以后，还需要一个很重要的环节—— 就是邮件提醒。不管是任务执行成功还是失败，都可以发送邮件提醒。这样每天晚上收到任务成功的消息，就可以安心睡觉了。

因此，本篇就带你来看看如何在Oozie中使用Email。

Email Action

在Oozie中每个工作流的环节都被设计成一个Action，email就是其中的一个Action.

Email action可以在oozie中发送信息，在email action中必须指定接收的地址，主题subject和内容body。在接收地址参数中支持使用逗号分隔，添加多个邮箱地址。

email action是同步执行的，因此必须等到邮件发出后，这个action才算完成，才能执行下一个action。

email action里面的所有参数都可以使用EL表达式。

语法规则

  1. <workflow-app name="[WF-DEF-NAME]" xmlns="uri:oozie:workflow:0.1">
  2.     ...
  3.     <action name="[NODE-NAME]">
  4.         <email xmlns="uri:oozie:email-action:0.2">
  5.             <to>[COMMA-SEPARATED-TO-ADDRESSES]</to>
  6.             <cc>[COMMA-SEPARATED-CC-ADDRESSES]</cc> <!-- cc is optional -->
  7.             <subject>[SUBJECT]</subject>
  8.             <body>[BODY]</body>
  9.             <content_type>[CONTENT-TYPE]</content_type> <!-- content_type is optional -->
  10.             <attachment>[COMMA-SEPARATED-HDFS-FILE-PATHS]</attachment> <!-- attachment is optional -->
  11.         </email>
  12.         <ok to="[NODE-NAME]"/>
  13.         <error to="[NODE-NAME]"/>
  14.     </action>
  15.     ...
  16. </workflow-app>

to和cc命令指定了谁来接收邮件。可以通过逗号分隔来指定多个邮箱地址。to是必填项，cc是可选的。

主题subject和正文body用于指定邮件的标题和正文，email-action:0.2支持text/html这种格式的正文，默认是普通的文本"text/plain"

attachment用于在邮件中添加一个hdfs文件的附件，也可以通过逗号分隔符指定多个附件。如果路径声明的不全，那么也会被当做hdfs中的文件。本地文件是不能添加到附件中的。

配置

email action需要在oozie-site.xml中配置SMTP服务器配置。下面是需要配置的值：

oozie.email.smtp.host

这个值是SMTP服务器的地址，默认是loalhost

oozie.email.smtp.port

是SMTP服务器的端口号，默认是25.

oozie.email.from.address

发送邮件的地址，默认是oozie@localhost

oozie.email.smtp.auth

是否开启认证，默认不开启

oozie.email.smtp.username

如果开启认证，登录的用户名，默认是空

oozie.email.smtp.password

如果开启认证，用户对应的密码，默认是空

PS. 在linux可以通过find -name oozie-site.xml在当前目录下查找。在我们的CDH版本中这个文件在./etc/oozie/conf.dist/oozie-site.xml

遇到的问题

很多人会遇到无法发邮件的问题，首先是要开启SMTP服务，查看是否开启可以使用telnet localhost 25。

另外，如果使用的是企业邮箱，需要注意发件人的格式，必须符合企业邮箱的设置。并且收件人只能是企业邮箱的地址。

在Cloudera Mnager中的配置如下图：

样例

  1. <workflow-app name="sample-wf" xmlns="uri:oozie:workflow:0.1">
  2.     ...
  3.     <action name="an-email">
  4.         <email xmlns="uri:oozie:email-action:0.1">
  5.             <to>bob@initech.com,the.other.bob@initech.com</to>
  6.             <cc>will@initech.com</cc>
  7.             <subject>Email notifications for ${wf:id()}</subject>
  8.             <body>The wf ${wf:id()} successfully completed.</body>
  9.         </email>
  10.         <ok to="myotherjob"/>
  11.         <error to="errorcleanup"/>
  12.     </action>
  13.     ...
  14. </workflow-app>

上面的例子中，邮件发给了bob,the.other.bob以及抄送给will，并指定了邮件的标题和正文以及workflow的id。

附录

为了更多的了解Oozie，这里直接给出了Oozie相关的重要配置

oozie-site.xml配置

  1. <?xml version="1.0"?>
  2. <configuration>
  3.     <!--oozie-default.xml文件是默认的配置-->
  4.     <property>
  5.         <name>oozie.service.ProxyUserService.proxyuser.hue.hosts</name>
  6.         <value>*</value>
  7.     </property>
  8.     <property>
  9.         <name>oozie.service.ProxyUserService.proxyuser.hue.groups</name>
  10.         <value>*</value>
  11.     </property>
  12. </configuration>

oozie-defualt.xml

  1. <?xml version="1.0"?>
  2. <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
  3. <!--
  4.   Licensed to the Apache Software Foundation (ASF) under one
  5.   or more contributor license agreements.  See the NOTICE file
  6.   distributed with this work for additional information
  7.   regarding copyright ownership.  The ASF licenses this file
  8.   to you under the Apache License, Version 2.0 (the
  9.   distributed under the License is distributed on an "AS IS" BASIS,
  10.   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  11.   See the License for the specific language governing permissions and
  12.   limitations under the License.
  13. -->
  14. <configuration>
  16.     <!-- ************************** VERY IMPORTANT  ************************** -->
  17.     <!-- This file is in the Oozie configuration directory only for reference. -->
  18.     <!-- It is not loaded by Oozie, Oozie uses its own privatecopy.            -->
  19.     <!-- ************************** VERY IMPORTANT  ************************** -->
  21.     <property>
  22.         <name>oozie.output.compression.codec</name>
  23.         <value>gz</value>
  24.         <description>
  25.             The name of the compression codec to use.
  26.             where codec class implements the interface org.apache.oozie.compression.CompressionCodec.
  27.             If oozie.compression.codecs is not specified, gz codec implementation is used by default.
  28.         </description>
  29.     </property>
  31.     <property>
  32.         <name>oozie.action.mapreduce.uber.jar.enable</name>
  33.         <value>false</value>
  34.         <description>
  35.             which specify the oozie.mapreduce.uber.jar configuration property will fail.
  36.         </description>
  37.     </property>
  39.     <property>
  40.         <name>oozie.processing.timezone</name>
  41.         <value>UTC</value>
  42.         <description>
  43.             is changed, note that GMT(+/-)#### timezones do not observe DST changes.
  44.         </description>
  45.     </property>
  47.     <!-- Base Oozie URL: <SCHEME>://<HOST>:<PORT>/<CONTEXT> -->
  49.     <property>
  50.         <name>oozie.base.url</name>
  51.         <value>http://localhost:8080/oozie</value>
  52.         <description>
  53.              Base Oozie URL.
  54.         </description>
  55.     </property>
  57.     <!-- Services -->
  59.     <property>
  60.         <name>oozie.system.id</name>
  61.         <value>oozie-${user.name}</value>
  62.         <description>
  63.             The Oozie system ID.
  64.         </description>
  65.     </property>
  67.     <property>
  68.         <name>oozie.systemmode</name>
  69.         <value>NORMAL</value>
  70.         <description>
  71.             System mode for  Oozie at startup.
  72.         </description>
  73.     </property>
  75.     <property>
  76.         <name>oozie.delete.runtime.dir.on.shutdown</name>
  77.         <value>true</value>
  78.         <description>
  79.             If the runtime directory should be kept after Oozie shutdowns down.
  80.         </description>
  81.     </property>
  83.     <property>
  84.         <name>oozie.services</name>
  85.         <value>
  86.             org.apache.oozie.service.SchedulerService,
  87.             org.apache.oozie.service.InstrumentationService,
  88.             org.apache.oozie.service.MemoryLocksService,
  89.             org.apache.oozie.service.UUIDService,
  90.             org.apache.oozie.service.ELService,
  91.             org.apache.oozie.service.AuthorizationService,
  92.             org.apache.oozie.service.UserGroupInformationService,
  93.             org.apache.oozie.service.HadoopAccessorService,
  94. /email
  95.             IMPORTANT: if the StoreServicePasswordService is active, it will reset this value with the
  96. value given in
  97.                        the console.
  98.         </description>
  99.     </property>
  101.     <property>
  102.         <name>oozie.service.JPAService.pool.max.active.conn</name>
  103.         <value>10</value>
  104.         <description>
  105.              Max number of connections.
  106.         </description>
  107.     </property>
  109.    <!-- SchemaService -->
  111.     <property>
  112.         <name>oozie.service.SchemaService.wf.schemas</name>
  113.         <value>
  114.             oozie-workflow-0.1.xsd,oozie-workflow-0.2.xsd,oozie-workflow-0.2.5.xsd,oozie-workflow-0.3.x
  115. sd,oozie-workflow-0.4.xsd,
  116.             oozie-workflow-0.4.5.xsd,oozie-workflow-0.5.xsd,
  117.             shell-action-0.1.xsd,shell-action-0.2.xsd,shell-action-0.3.xsd,
  118.             email-action-0.1.xsd,email-action-0.2.xsd,
  119.             hive-action-0.2.xsd,hive-action-0.3.xsd,hive-action-0.4.xsd,hive-action-0.5.xsd,hive-action
  120. -0.6.xsd,
  121.             sqoop-action-0.2.xsd,sqoop-action-0.3.xsd,sqoop-action-0.4.xsd,
  122.             ssh-action-0.1.xsd,ssh-action-0.2.xsd,
  123.             distcp-action-0.1.xsd,distcp-action-0.2.xsd,
  124.             oozie-sla-0.1.xsd,oozie-sla-0.2.xsd,
  125.             hive2-action-0.1.xsd, hive2-action-0.2.xsd,
  126.             spark-action-0.1.xsd,spark-action-0.2.xsd
  127.         </value>
  128.         <description>
  129.             List of schemas for workflows (separated by commas).
  130.         </description>
  131.     </property>
  133.     <property>
  134.         <name>oozie.service.SchemaService.wf.ext.schemas</name>
  135.         <value> </value>
  136.         <description>
  137.             List of additional schemas for workflows (separated by commas).
  138.         </description>
  139.     </property>
  141.     <property>
  142.         <name>oozie.service.SchemaService.coord.schemas</name>
  143. /email
  144.         <description>
  145.              Base console URL for a workflow job.
  146.         </description>
  147.     </property>
  149.     <!-- ActionService -->
  151.     <property>
  152.         <name>oozie.service.ActionService.executor.classes</name>
  153.         <value>
  154.             org.apache.oozie.action.decision.DecisionActionExecutor,
  155.             org.apache.oozie.action.hadoop.JavaActionExecutor,
  156.             org.apache.oozie.action.hadoop.FsActionExecutor,
  157.             org.apache.oozie.action.hadoop.MapReduceActionExecutor,
  158.             org.apache.oozie.action.hadoop.PigActionExecutor,
  159.             org.apache.oozie.action.hadoop.HiveActionExecutor,
  160.             org.apache.oozie.action.hadoop.ShellActionExecutor,
  161.             org.apache.oozie.action.hadoop.SqoopActionExecutor,
  162.             org.apache.oozie.action.hadoop.DistcpActionExecutor,
  163.             org.apache.oozie.action.hadoop.Hive2ActionExecutor,
  164.             org.apache.oozie.action.ssh.SshActionExecutor,
  165.             org.apache.oozie.action.oozie.SubWorkflowActionExecutor,
  166.             org.apache.oozie.action.email.EmailActionExecutor,
  167.             org.apache.oozie.action.hadoop.SparkActionExecutor
  168.         </value>
  169.         <description>
  170.             List of ActionExecutors classes (separated by commas).
  171.             Only action types with associated executors can be used in workflows.
  172.         </description>
  173.     </property>
  175.     <property>
  176.         <name>oozie.service.ActionService.executor.ext.classes</name>
  177.         <value> </value>
  178.         <description>
  179.             List of ActionExecutors extension classes (separated by commas). Only action types with ass
  180. ociated
  181.             executors can be used in workflows. This property is a convenience property to add extensio
  182. ns to the built
  183.             in executors without having to include all the built in ones.
  184.         </description>
  185.     </property>
  187.     <!-- ActionCheckerService -->
  189.     <property>
  190.         <name>oozie.service.ActionCheckerService.action.check.interval</name>
  191. /email
  192.         <description>
  193.             Comma separated AUTHORITY=SPARK_CONF_DIR, where AUTHORITY is the HOST:PORT of
  194.             the ResourceManager of a YARN cluster. The wildcard '*' configuration is
  195.             used when there is no exact match for an authority. The SPARK_CONF_DIR contains
  196.             the relevant spark-defaults.conf properties file. If the path is relative is looked within
  197.             the Oozie configuration directory; though the path can be absolute.  This is only used
  198.             when the Spark master is set to either "yarn-client" or "yarn-cluster".
  199.         </description>
  200.     </property>
  202.     <property>
  203.         <name>oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jar</name>
  204.         <value>true</value>
  205.         <description>
  206.             If true, Oozie will ignore the "spark.yarn.jar" property from any Spark configurations spec
  207. ified in
  208.             oozie.service.SparkConfigurationService.spark.configurations.  If false, Oozie will not ign
  209. ore it.  It is recommended
  210.             to leave this as true because it can interfere with the jars in the Spark sharelib.
  211.         </description>
  212.     </property>
  214.     <property>
  215.         <name>oozie.email.attachment.enabled</name>
  216.         <value>true</value>
  217.         <description>
  218.             This value determines whether to support email attachment of a file on HDFS.
  219.             Set it false if there is any security concern.
  220.         </description>
  221.     </property>
  223.     <property>
  224.         <name>oozie.actions.default.name-node</name>
  225.         <value> </value>
  226.         <description>
  227.             The default value to use for the &lt;name-node&gt; element in applicable action types.  Thi
  228. s value will be used when
  229.             neither the action itself nor the global section specifies a &lt;name-node&gt;.  As expecte
  230. d, it should be of the form
  231.             "hdfs://HOST:PORT".
  232.         </description>
  233.     </property>
  235.     <property>
  236.         <name>oozie.actions.default.job-tracker</name>
  237.         <value> </value>
  238.         <description>
  239. @
  240. search hit BOTTOM, continuing at TOP
  241.             IMPORTANT: if the StoreServicePasswordService is active, it will reset this value with the
  242. value given in
  243.                        the console.
  244.         </description>
  245.     </property>
  247.     <property>
  248.         <name>oozie.service.JPAService.pool.max.active.conn</name>
  249.         <value>10</value>
  250.         <description>
  251.              Max number of connections.
  252.         </description>
  253.     </property>
  255.    <!-- SchemaService -->
  257.     <property>
  258.         <name>oozie.service.SchemaService.wf.schemas</name>
  259.         <value>
  260.             oozie-workflow-0.1.xsd,oozie-workflow-0.2.xsd,oozie-workflow-0.2.5.xsd,oozie-workflow-0.3.x
  261. sd,oozie-workflow-0.4.xsd,
  262.             oozie-workflow-0.4.5.xsd,oozie-workflow-0.5.xsd,
  263.             shell-action-0.1.xsd,shell-action-0.2.xsd,shell-action-0.3.xsd,
  264.             email-action-0.1.xsd,email-action-0.2.xsd,
  265.             hive-action-0.2.xsd,hive-action-0.3.xsd,hive-action-0.4.xsd,hive-action-0.5.xsd,hive-action
  266. -0.6.xsd,
  267.             sqoop-action-0.2.xsd,sqoop-action-0.3.xsd,sqoop-action-0.4.xsd,
  268.             ssh-action-0.1.xsd,ssh-action-0.2.xsd,
  269.             distcp-action-0.1.xsd,distcp-action-0.2.xsd,
  270.             oozie-sla-0.1.xsd,oozie-sla-0.2.xsd,
  271.             hive2-action-0.1.xsd, hive2-action-0.2.xsd,
  272.             spark-action-0.1.xsd,spark-action-0.2.xsd
  273.         </value>
  274.         <description>
  275.             List of schemas for workflows (separated by commas).
  276.         </description>
  277.     </property>
  279.     <property>
  280.         <name>oozie.service.SchemaService.wf.ext.schemas</name>
  281.         <value> </value>
  282.         <description>
  283.             List of additional schemas for workflows (separated by commas).
  284.         </description>
  285.     </property>
  287.     <property>
  288.         <name>oozie.service.SchemaService.coord.schemas</name>
  289. /email
  290.         <description>
  291.              Base console URL for a workflow job.
  292.         </description>
  293.     </property>
  295.     <!-- ActionService -->
  297.     <property>
  298.         <name>oozie.service.ActionService.executor.classes</name>
  299.         <value>
  300.             org.apache.oozie.action.decision.DecisionActionExecutor,
  301.             org.apache.oozie.action.hadoop.JavaActionExecutor,
  302.             org.apache.oozie.action.hadoop.FsActionExecutor,
  303.             org.apache.oozie.action.hadoop.MapReduceActionExecutor,
  304.             org.apache.oozie.action.hadoop.PigActionExecutor,
  305.             org.apache.oozie.action.hadoop.HiveActionExecutor,
  306.             org.apache.oozie.action.hadoop.ShellActionExecutor,
  307.             org.apache.oozie.action.hadoop.SqoopActionExecutor,
  308.             org.apache.oozie.action.hadoop.DistcpActionExecutor,
  309.             org.apache.oozie.action.hadoop.Hive2ActionExecutor,
  310.             org.apache.oozie.action.ssh.SshActionExecutor,
  311.             org.apache.oozie.action.oozie.SubWorkflowActionExecutor,
  312.             org.apache.oozie.action.email.EmailActionExecutor,
  313.             org.apache.oozie.action.hadoop.SparkActionExecutor
  314.         </value>
  315.         <description>
  316.             List of ActionExecutors classes (separated by commas).
  317.             Only action types with associated executors can be used in workflows.
  318.         </description>
  319.     </property>
  321.     <property>
  322.         <name>oozie.service.ActionService.executor.ext.classes</name>
  323.         <value> </value>
  324.         <description>
  325.             List of ActionExecutors extension classes (separated by commas). Only action types with ass
  326. ociated
  327.             executors can be used in workflows. This property is a convenience property to add extensio
  328. ns to the built
  329.             in executors without having to include all the built in ones.
  330.         </description>
  331.     </property>
  333.     <!-- ActionCheckerService -->
  335.     <property>
  336.         <name>oozie.service.ActionCheckerService.action.check.interval</name>
  337. /email
  338.         <description>
  339.             used when there is no exact match for an authority. The SPARK_CONF_DIR contains
  340.             the relevant spark-defaults.conf properties file. If the path is relative is looked within
  341.             the Oozie configuration directory; though the path can be absolute.  This is only used
  342.             when the Spark master is set to either "yarn-client" or "yarn-cluster".
  343.         </description>
  344.     </property>
  346.     <property>
  347.         <name>oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jar</name>
  348.         <value>true</value>
  349.         <description>
  350.             If true, Oozie will ignore the "spark.yarn.jar" property from any Spark configurations spec
  351. ified in
  352.             oozie.service.SparkConfigurationService.spark.configurations.  If false, Oozie will not ign
  353. ore it.  It is recommended
  354.             to leave this as true because it can interfere with the jars in the Spark sharelib.
  355.         </description>
  356.     </property>
  358.     <property>
  359.         <name>oozie.email.attachment.enabled</name>
  360.         <value>true</value>
  361.         <description>
  362.             This value determines whether to support email attachment of a file on HDFS.
  363.             Set it false if there is any security concern.
  364.         </description>
  365.     </property>
  367.     <property>
  368.         <name>oozie.actions.default.name-node</name>
  369.         <value> </value>
  370.         <description>
  371.             The default value to use for the &lt;name-node&gt; element in applicable action types.  Thi
  372. s value will be used when
  373.             neither the action itself nor the global section specifies a &lt;name-node&gt;.  As expecte
  374. d, it should be of the form
  375.             "hdfs://HOST:PORT".
  376.         </description>
  377.     </property>
  379.     <property>
  380.         <name>oozie.actions.default.job-tracker</name>
  381.         <value> </value>
  382.         <description>
  383.             The default value to use for the &lt;job-tracker&gt; element in applicable action types.  T
  384. his value will be used when
  385.             neither the action itself nor the global section specifies a &lt;job-tracker&gt;.  As expec
  386. ted, it should be of the form
  387.             "HOST:PORT".
  388.         </description>
  389.     </property>
  391. </configuration>

Oozie分布式任务的工作流——邮件篇的更多相关文章

  1. Oozie分布式任务的工作流——脚本篇

    继前一篇大体上翻译了Email的Action配置,本篇继续看一下Shell的相关配置. Shell Action Shell Action可以执行Shell脚本命令,工作流会等到shell完全执行完毕 ...

  2. Oozie分布式任务的工作流——Spark篇

    Spark是现在应用最广泛的分布式计算框架,oozie支持在它的调度中执行spark.在我的日常工作中,一部分工作就是基于oozie维护好每天的spark离线任务,合理的设计工作流并分配适合的参数对于 ...

  3. Oozie分布式任务的工作流——Sqoop篇

    Sqoop的使用应该是Oozie里面最常用的了,因为很多BI数据分析都是基于业务数据库来做的,因此需要把mysql或者oracle的数据导入到hdfs中再利用mapreduce或者spark进行ETL ...

  4. 分布式协调服务Zookeeper扫盲篇

    分布式协调服务Zookeeper扫盲篇 作者:尹正杰 版权声明:原创作品,谢绝转载!否则将追究法律责任. 身为运维工程师对kubernetes(k8s)可能比较熟,那么etcd(go语言实现)分布式协 ...

  5. [源码解析] PyTorch 分布式(8) -------- DistributedDataParallel之论文篇

    [源码解析] PyTorch 分布式(8) -------- DistributedDataParallel之论文篇 目录 [源码解析] PyTorch 分布式(8) -------- Distrib ...

  6. [源码解析] PyTorch分布式优化器(1)----基石篇

    [源码解析] PyTorch分布式优化器(1)----基石篇 目录 [源码解析] PyTorch分布式优化器(1)----基石篇 0x00 摘要 0x01 从问题出发 1.1 示例 1.2 问题点 0 ...

  7. Oozie分布式工作流——流控制

    最近又开始捅咕上oozie了,所以回头还是翻译一下oozie的文档.文档里面最重要就属这一章了--工作流定义. 一提到工作流,首先想到的应该是工作流都支持哪些工作依赖关系,比如串式的执行,或者一对多, ...

  8. Oozie分布式工作流——Action节点

    前篇讲述了下什么是流控制节点,本篇继续来说一下什么是 Action Nodes操作节点.Action节点有一些比较通用的特性: Action节点是远程的 所有oozie创建的计算和处理任务都是异步的, ...

  9. Oozie分布式工作流——从理论和实践分析使用节点间的参数传递

    Oozie支持Java Action,因此可以自定义很多的功能.本篇就从理论和实践两方面介绍下Java Action的妙用,另外还涉及到oozie中action之间的参数传递. 本文大致分为以下几个部 ...

随机推荐

  1. 一起学 Java（三） 集合框架、数据结构、泛型

    一.Java 集合框架 集合框架是一个用来代表和操纵集合的统一架构.所有的集合框架都包含如下内容: 接口:是代表集合的抽象数据类型.接口允许集合独立操纵其代表的细节.在面向对象的语言,接口通常形成一个 ...

  2. 隐私泄露杀手锏 —— Flash 权限反射

    [简版:http://weibo.com/p/1001603881940380956046] 前言 一直以为该风险早已被重视,但最近无意中发现,仍有不少网站存在该缺陷,其中不乏一些常用的邮箱.社交网站 ...

  3. ASP.NET Core 1.1 简介

    ASP.NET Core 1.1 于2016年11月16日发布.这个版本包括许多伟大的新功能以及许多错误修复和一般的增强.这个版本包含了多个新的中间件组件.针对Windows的WebListener服 ...

  4. 微信小程序初探

    做为码农相信大家最近肯定都会听到微信小程序,虽然现阶段还没有正式开放注册,但大家可以还是可以开发测试. 到微信的WIKI(http://mp.weixin.qq.com/wiki?t=resource ...

  5. bzoj1584--DP

    题目大意:有N头奶牛,每头那牛都有一个标号Pi,1 <= Pi <= M <= N <= 40000.现在Farmer John要把这些奶牛分成若干段,定义每段的不河蟹度为:若 ...

  6. 子类继承父类时JVM报出Error：Implicit super constructor People() is undefined for default constructor. Must define an explicit constructor

    当子类继承父类的时候,若父类没有定义带参的构造方法,则子类可以继承父类的默认构造方法 当父类中定义了带参的构造方法,子类必须显式的调用父类的构造方法 若此时,子类还想调用父类的默认构造方法,必须在父类 ...

  7. spring的BeanFactory加载过程

    ApplicationContext spring = new ClassPathXmlApplicationContext("classpath*:spring/applicationCo ...

  8. 学习C的笔记

    [unsigned] 16位系统中一个int能存储的数据的范围为-32768~32767,而unsigned能存储的数据范围则是0~65535.由于在计算机中,整数是以补码形式存放的.根据最高位的不同 ...

  9. Linux程序包管理之rpm

    rpm简介 rpm( Red Hat Package Manager )是一个开放的软件包管理系统.它工作于Red Hat Linux及其他Linux系统,成为Linux中公认的软件包管理标准. rp ...

  10. 开始webservice了

    一.WebService到底是什么 一言以蔽之:WebService是一种跨编程语言和跨操作系统平台的远程调用技术. 所谓跨编程语言和跨操作平台,就是说服务端程序采用java编写,客户端程序则可以采用 ...