logstash-input-jdbc - GitLite

KO | EN

gitlite — search

#markdown #anthropic #rust #pytorch #cpp #video #shell #postgresql #ai-agent #php

logstash-input-jdbc

(★ 443)

Logstash Plugin for JDBC Inputs

파일 탐색기

ZIP 다운로드

- - changelog-version-update.yml
  - unit-tests.yml
- CONTRIBUTING.md
- ISSUE_TEMPLATE.md
- PULL_REQUEST_TEMPLATE.md
- - docker-compose.yml
  - docker-run.sh
  - docker-setup.sh
  - Dockerfile
  - run.sh
  - setup.sql
- index.asciidoc
- - integ_spec.rb
  - jdbc_spec.rb
.gitignore
CHANGELOG.md
Gemfile
LICENSE
logstash-input-jdbc.gemspec
NOTICE.TXT
Rakefile
README.md
version

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

명령어 용어집

이 문서에서 사용된 명령어를 모아봤습니다. 낯선 명령어가 있다면 펼쳐서 확인해보세요.

🔍

`bundle`

설명 보기 ▼

Ruby 프로그래밍 언어의 종속성 관리자.
더 많은 정보: <https://bundler.io/man/bundle.1.html>.

bundle install

작업 디렉토리에 있는 `Gemfile`에 정의된 모든 gem을 설치:

bundle exec {{command}} {{arguments}}

현재 번들의 컨텍스트에서 명령을 실행:

bundle update

`Gemfile` 에 정의된 규칙에 따라 모든 gem을 업데이트 하고 `Gemfile.lock`을 재생성:

🔍

`gem`

설명 보기 ▼

Ruby 프로그래밍 언어용 패키지 관리자.
더 많은 정보: <https://guides.rubygems.org/command-reference/>.

gem search {{regex}} {{[-a|--all]}}

원격 gem을 검색하고 사용 가능한 모든 버전을 표시:

gem install {{gem_name}}

최신 버전의 gem을 설치:

gem install {{gem_name}} {{[-v|--version]}} {{1.0.0}}

특정 버전의 gem을 설치:

🔍

`rake`

설명 보기 ▼

Ruby용 Make와 유사한 프로그램.
`rake`의 작업은 Rakefile에 지정됩니다.
더 많은 정보: <https://ruby.github.io/rake/>.

rake

`default` Rakefile 작업 실행:

rake {{task}}

특정 작업 실행:

rake --jobs {{n}}

동시에 `n`개의 작업 병렬 실행 (기본값은 CPU 코어 수 + 4):

# 프로젝트 배지

Unit Tests 바로가기

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

This is a plugin for [Logstash](https://github.com/elastic/logstash).

It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.

## JDBC Input Plugin Has Moved

This JDBC Input Plugin is now a part of the [JDBC Integration Plugin][integration-source];
this project remains open for backports of fixes from that project to the 5.x series where possible, but issues should first be filed on the [integration plugin][integration-issues].

[integration-source]: https://github.com/logstash-plugins/logstash-integration-jdbc
[integration-issues]: https://github.com/logstash-plugins/logstash-integration-jdbc/issues/

## Documentation

Logstash provides infrastructure to automatically generate documentation for this plugin. We use the asciidoc format to write documentation so any comments in the source code will be first converted into asciidoc and then into html. All plugin documentation are placed under one [central location](http://www.elastic.co/guide/en/logstash/current/).

- For formatting code or config example, you can use the asciidoc `[source,ruby]` directive
- For more asciidoc formatting tips, see the excellent reference here https://github.com/elastic/docs#asciidoc-guide

## Need Help?

Need help? Try #logstash on freenode IRC or the https://discuss.elastic.co/c/logstash discussion forum.

## Developing

### 1. Plugin Developement and Testing

#### Code
- To get started, you'll need JRuby with the Bundler gem installed.

- Create a new plugin or clone and existing from the GitHub [logstash-plugins](https://github.com/logstash-plugins) organization.

- Install dependencies
```sh
bundle install
```

#### Test

```sh
bundle exec rspec
```

The Logstash code required to run the tests/specs is specified in the `Gemfile` by the line similar to:
```ruby
gem "logstash", :github => "elasticsearch/logstash", :branch => "1.5"
```
To test against another version or a local Logstash, edit the `Gemfile` to specify an alternative location, for example:
```ruby
gem "logstash", :github => "elasticsearch/logstash", :ref => "master"
```
```ruby
gem "logstash", :path => "/your/local/logstash"
```

Then update your dependencies and run your tests:

```sh
bundle install
bundle exec rspec
```

### 2. Running your unpublished Plugin in Logstash

#### 2.1 Run in a local Logstash clone

- Edit Logstash `tools/Gemfile` and add the local plugin path, for example:
```ruby
gem "logstash-input-jdbc", :path => "/your/local/logstash-input-jdbc"
```
- Update Logstash dependencies
```sh
rake vendor:gems
```
- Run Logstash with your plugin
```sh
bin/logstash -e 'input {jdbc {..}}'
```
At this point any modifications to the plugin code will be applied to this local Logstash setup. After modifying the plugin, simply rerun Logstash.

#### 2.2 Run in an installed Logstash

- Build your plugin gem
```sh
gem build logstash-input-jdbc.gemspec
```
- Install the plugin from the Logstash home
```sh
bin/plugin install /your/local/plugin/logstash-input-jdbc.gem
```
- Start Logstash and proceed to test the plugin

## Example configuration

Reading data from MySQL:

input {
	  jdbc {
	    jdbc_driver_library => "/path/to/mysql-connector-java-5.1.33-bin.jar"
	    jdbc_driver_class => "com.mysql.jdbc.Driver"
	    jdbc_connection_string => "jdbc:mysql://host:port/database"
	    jdbc_user => "user"
	    jdbc_password => "password"
      # or jdbc_password_filepath => "/path/to/my/password_file"
	    statement => "SELECT ..."
	    jdbc_paging_enabled => "true"
	    jdbc_page_size => "50000"
	  }
	}

filter {
	  [some filters here]
	}

output {
	  stdout {
	    codec => rubydebug
	  }
	  elasticsearch_http {
	    host => "host"
	    index => "myindex"
	  }
	}

## Contributing

All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.

Programming is not a required skill. Whatever you've seen about open source and maintainers or community members  saying "send patches or die" - you will not see that here.

It is more important to me that you are able to contribute.

For more information about contributing, see the [CONTRIBUTING](https://github.com/elastic/logstash/blob/master/CONTRIBUTING.md) file.