terça-feira, 8 de abril de 2014

How to use the Path Hierarchy Tokenizer in ElasticSearch

How to use the Path Hierarchy Tokenizer:

0. If you and just to check the output of this tokenizer, you can run:

curl -XGET 'localhost:9200/_analyze?tokenizer=path_hierarchy&filters=lowercase' -d '/something/something/else'


1. Put a map:

$ curl -XPUT localhost:9200/index_files3/ -d '
{
  "settings":{
     "index":{
        "analysis":{
           "analyzer":{
              "analyzer_path_hierarchy":{
                 "tokenizer":"my_path_hierarchy_tokenizer",
                 "filter":"lowercase"
              }
           },
       "tokenizer" : {
              "my_path_hierarchy_tokenizer" : {
                  "type" : "path_hierarchy",
                  "delimiter" : "/",
                  "replacement" : "*",
                  "buffer_size" : "1024",
                  "reverse" : "true",
                  "skip" : "0"
               }
           }
        }
     }
  },
  "mappings":{
     "file":{
        "properties":{
           "path":{
              "analyzer":"analyzer_path_hierarchy",
              "type":"string"
           }
        }
     }
  }
}'


2. Get the map:

curl -XGET 'http://localhost:9200/index_files3/file/_mapping'


3. Add a new document:

$ curl -XPUT 'http://localhost:9200/index_files3/file/1' -d '{
    "name" : "c1",
    "text" : "t1",
    "path" : "/c1/c2/c3"
}'


4. Check if it is there:

$ curl -XGET 'http://localhost:9200/index_files3/file/1'


5. Search:

Fail: curl -XGET 'http://localhost:9200/index_files3/_search?q=path:c1'

Success: curl -XGET 'http://localhost:9200/index_files3/_search?q=path://c1'

segunda-feira, 24 de março de 2014

Error: Could not find or load main class org.codehaus.classworlds.Launcher


$ which mvn

$ sudo apt-get install maven

$ mvn -version

The command apt-get install the Maven in /usr/share/maven, then

export M2_HOME=/usr/share/maven
export M2=%M2_HOME%\bin

PATH=$PATH:$JAVA_HOME
PATH=$PATH:$M2
export PATH


http://www.cubeia.com/2009/02/10-sure-signs-you-are-doing-maven-wrong/

terça-feira, 18 de março de 2014

Regular expression (regex) for JDBC connection string/URL

Regular expression (regex) for JDBC connection string/URL

String regex= "(^jdbc:"+databaseName.toLowerCase()+":){1,1}\\S*(:?)(//+)\\S*(/+)\\S+";

Good place to test:

http://java-regex-tester.appspot.com/

quinta-feira, 13 de março de 2014

[RASCUNHO] Cola (cheatsheet) para problemas na instalação de MySQL no Ubuntu


Purge
sudo apt-get purge mysql-server mysql-client mysql-common mysql-client-5.5 mysql-server-5.5 sudo apt-get purge mariadb-server-5.5
sudo apt-get purge mariadb

Remove

sudo rm -rf mysql.dpkg-bak
sudo apt-get remove mysql-server mysql-client mysql-common
sudo apt-get autoremove
sudo rm -rf /var/lib/mysql
sudo deluser mysql

Install

sudo apt-get install mysql-server-core-5.5
sudo apt-get install -f mysql-server (-fix)
sudo apt-get install -f libaio1
 

Install from deb pack

sudo dpkg -i mysql-5.6.13-debian6.0-i686.deb

Logs/status

service mysql status
ps ax | grep mysql
grep mysql /var/log/syslog
grep mysql /var/log/daemon.log
sudo netstat -tap | grep mysql
sudo service mysql restart
mysql –version
which mysql

DPKG

sudo dpkg --configure -a
sudo rm /var/lib/dpkg/lock
sudo rm /var/cache/apt/archives/lock
sudo dpkg -S etc/mysql

Check


sudo apt-get remove --purge mysql-server mysql-client mysql-common
sudo apt-get autoremove
sudo apt-get autoclean
sudo deluser mysql
sudo rm -rf /var/lib/mysql


Connection URL



jdbc:mysql://localhost:3306/test







Reference

https://rtcamp.com/tutorials/mysql/mysql-5-6-ubuntu-12-04/

terça-feira, 11 de março de 2014

Instalando Jenkins e o plugin JMeter (plugin Performance)

Jenkins

1. O procedimento de instalação pode ser encontrado em:

https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Red+Hat+distributions

2. Verifique se ele está funcionando :

[root@spike ~]# sudo service jenkins start
Starting Jenkins                                           [  OK  ]

Os logs de Jenkins prazo será colocado em:
/ var / log / Jenkins / jenkins.log
Encontre algo como:
INFO: Jenkins está totalmente instalado e funcionando
3 Acessando Jenkins :

A informação geral pode ser encontrada em :
https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins
No entanto, é necessário criar um túnel na porta 8080.
ssh- f root @ spike- L 8080:127.0.0.1:8080 -N
Jenkins deve estar disponível em :
http://127.0.0.1:8080/

plugins JMeter

As páginas Jenkins recomenda a utilização do plugin do Desempenho em vez de JMeter plugin.

https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin
A maneira mais fácil de instalar é Jenkins pela interface Plugin Representante: http://127.0.0.1:8080/pluginManager/
Vá na aba " disponível" e encontrar " plug-in de desempenho" ( figura abaixo)
Vá para " download agora e instale depois restart"
Depois de terminar o donwload , reinicie o serviço Jenkins : " jenkins serviço sudo restart"
instale JMeter
Faça o download :
wget http://apache.mirror.iphh.net//jmeter/binaries/apache-jmeter-2.11.tgz
Extraia os arquivos para :/ var / lib / Jenkins
Renomear ( mv ) apache- jmeter 2.11 como jmeter
Para verificar se ele está instalado , é necessário criar um novo emprego.
New Job
Projeto de software free-style
Sob Build, selecionar Invoke Formiga
Selecione Avançado
Público-alvo: todos
Build Path : / var / lib / Jenkins / jobs / MY_PROJECT_NAME / build.xml
Propriedades: jmeter.dir = / var / lib / Jenkins / JMeter ( referência para a etapa 5.c )
Down in Post- construir ações verifique a caixa de seleção Publicar Desempenho relatório de resultado de teste
Adicionar uma nova caixa de relatório e escolha JMeter
Definir o ramo de construir a JMeter
Para arquivos de relatório Especifique ** / *. JTL
Adicione o build.xml na raiz da pasta de trabalho ( / var / lib / Jenkins / jobs / MY_PROJECT_NAME / ) . No final eu adicionei um arquivo build.xml .
Pasta de Sub- the-job ( / var / lib / Jenkins / jobs / MY_PROJECT_NAME / ), crie a seguinte estrutura de diretório (a pasta da área de trabalho e todos os sub-pasta que tem que ser em chmod 777 " chmod -R 0777 / *") .
+ Scripts
+ Workspace
+ + Resultados
+ + + + JTL
+ + + + HTML
Na pasta scripts de carregar os scripts JMeter arquivos * . JMX

[RASCUNHO] Coleção de textos sobre como modificar a função de similaridade do ElasticSearch

It is necessary to extends the classes:
org.apache.lucene.search.similarities.Similarity;
org.elasticsearch.index.similarity.AbstractSimilarityProvider;

Since the ES 0.9 it is possible to change the similarity function to each field. This document explains how:
http://elasticsearchserverbook.com/elasticsearch-0-90-similarities/

General information:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-similarity.html

sexta-feira, 21 de fevereiro de 2014

Installing Jekins and the JMeter plugin (Performance plugin)

Jekins
1. The installation procedure can be found at:

https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Red+Hat+distributions

2. Check if it is working:
[root@spike ~]# sudo service jenkins start
Starting Jenkins                                           [  OK  ]
The logs of Jekins run will be placed at:
/var/log/jenkins/jenkins.log
Find something like:
INFO: Jenkins is fully up and running
3. Accessing Jekins:

The general information can be found on:
https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins
However, it is necessary to create a tunnel in the port 8080.
ssh -f root@spike -L 8080:127.0.0.1:8080 -N
Jekins must be available at:
http://127.0.0.1:8080/

JMeter plugins

The Jekins pages recommends using the Performance plugin instead of JMeter plugin.

https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin
  1. The easiest way to install Jekins is by the Plugin Manager interface: http://127.0.0.1:8080/pluginManager/
  2. Go in the tab "Available" and find "Performance plugin" (figure below) 
  3. Go in "Download now and install after restart"
  4. After finish the donwload, restart jekins service: "sudo service jenkins restart"
  5. Install JMeter
    1. Download it:
      wget http://apache.mirror.iphh.net//jmeter/binaries/apache-jmeter-2.11.tgz
    2. Extract the files to :/var/lib/jenkins
    3. Rename (mv) apache-jmeter-2.11 as jmeter
  6. To check if it is installed it is necessary to create a new job.
    1. New Job
    2. Free-style software project
    3. Under Build, select Invoke Ant
    4. Select Advanced
    5. Target : all
      Path Build : /var/lib/jenkins/jobs/MY_PROJECT_NAME/build.xml
      Properties : jmeter.dir=/var/lib/jenkins/jmeter (reference to step 5.c)
    6. Down in Post-build Actions check the Publish Performance test result report checkbox
    7. Add a new report box and choose JMeter
    8. Set the branch to build to JMeter
      For Report files specify **/*.jtl
  7. Add the build.xml at the root of the job folder (/var/lib/jenkins/jobs/MY_PROJECT_NAME/). At the end I added a build.xml file.
  8. Under the job folder (/var/lib/jenkins/jobs/MY_PROJECT_NAME/), create the following directory structure (the workspace folder and all it subfolder have to be in chmod 777 "chmod -R 0777 ./*").
    +scripts
    +workspace
    ++results
    ++++jtl
    ++++html
  9. In the scripts folder upload the JMeter scripts files *.jmx





Usefull references

http://www.theserverlabs.com/blog/2009/04/23/performance-tests-with-jmeter-maven-and-hudson/
http://jlorenzen.blogspot.de/2008/03/automated-performance-tests-using.html
http://neyto.blogspot.de/2013/02/install-jenkins-with-jmeter-performance_2208.html


Build xml:









   
       
   

    name="jmeter"
    classname="org.programmerplanet.ant.taskdefs.jmeter.JMeterTask"
    classpathref="ant.jmeter.classpath" >


   
   
   
   


             jmeterhome="${jmeter-home}"
         resultlogdir="workspace/results/jtl">
        
   




   
   



            classpathref="xslt.classpath"
        basedir="workspace/results/jtl"
        destdir="workspace/results/html"
        includes="*.jtl"
        style="${jmeter-home}/extras/jmeter-results-detail-report_21.xsl">