Mapper attachments pluginedit
The mapper attachments plugin has been deprecated in elasticsearch 5.0 and is now removed. You can use ingest attachment plugin instead.
elasticsearch 5.0에서 mapper attachments plugin은 deprecate되었고, 이제 제거되었다. 대신, ingest attachment plugin 을 사용할 수 있다.
S3 Repository pluginedit
The bucket an s3 repository is configured with will no longer be created automatically. It must exist before the s3 repository is created.
s3 repository가 설정된 bucket은 더 이상 자동으로 생성되지 않는다. s3 repository가 생성되기 전에 존재해야 한다.
Support for specifying s3 credentials through environment variables and system properties has been removed. Use the
elasticsearch-keystore
tool to securely store the credentials.환경 변수 및 system property를 통해, s3 credential을 지정하는 지원이 제거되었다. credential을 안전하게 저장하기 위해
elasticsearch-keystore
도구를 사용하자.Specifying region has been removed. This includes the settings
cloud.aws.region
,cloud.aws.s3.region
,repositories.s3.region
, and specifying region inside the repository settings. Instead, specify the full endpoint if a custom s3 location is needed, or rely on the default behavior which automatically locates the region of the configured bucket.region을 지정하는 기능이 제거되었다. 여기에는
cloud.aws.region
,cloud.aws.s3.region
,repositories.s3.region
설정과 repository 설정 내에서 region을 지정하는 것을 포함한다. 대신, 사용자 지정 s3 위치가 필요한 경우, full endpoint를 지정하거나 구성된 bucket의 region을 자동으로 찾는 기본 동작을 사용하자.Specifying s3 signer type has been removed, including
cloud.aws.signer
andcloud.aws.s3.signer
.cloud.aws.signer
와cloud.aws.s3.signer
을 포함하여, s3 signer type을 지정하는 것이 제거되었다.Global repositories settings have been removed. This includes
repositories.s3.bucket
,repositories.s3.server_side_encryption
,repositories.s3.buffer_size
,repositories.s3.max_retries
,repositories.s3.use_throttle_retries
,repositories.s3.chunk_size
,repositories.s3.compress
,repositories.s3.storage_class
,repositories.s3.canned_acl
,repositories.s3.base_path
, andrepositories.s3.path_style_access
. Instead, these settings should be set directly in the settings per repository. See S3 Repository settings.global repository 설정이 제거되었다. 여기에는
repositories.s3.bucket
,repositories.s3.server_side_encryption
,repositories.s3.buffer_size
,repositories.s3.max_retries
,repositories.s3.use_throttle_retries
,repositories.s3.chunk_size
,repositories.s3.compress
,repositories.s3.storage_class
,repositories.s3.canned_acl
,repositories.s3.base_path
그리고repositories.s3.path_style_access
을 포함한다. 대신 이 설정은 repository 별 설정에서 직접 설정되어야 한다.Shared client settings have been removed. This includes
cloud.aws.access_key
,cloud.aws.secret_key
,cloud.aws.protocol
,cloud.aws.proxy.host
,cloud.aws.proxy.port
,cloud.aws.proxy.username
,cloud.aws.proxy.password
,cloud.aws.signer
,cloud.aws.read_timeout
,cloud.aws.s3.access_key
,cloud.aws.s3.secret_key
,cloud.aws.s3.protocol
,cloud.aws.s3.proxy.host
,cloud.aws.s3.proxy.port
,cloud.aws.s3.proxy.username
,cloud.aws.s3.proxy.password
,cloud.aws.s3.signer
,cloud.aws.s3.read_timeout
,repositories.s3.access_key
,repositories.s3.secret_key
,repositories.s3.endpoint
andrepositories.s3.protocol
. Instead, use the new named client settings unders3.client.CLIENT_NAME.*
.공유 client 설정이 제거되었다.여기에는
cloud.aws.access_key
,cloud.aws.secret_key
,cloud.aws.protocol
,cloud.aws.proxy.host
,cloud.aws.proxy.port
,cloud.aws.proxy.username
,cloud.aws.proxy.password
,cloud.aws.signer
,cloud.aws.read_timeout
,cloud.aws.s3.access_key
,cloud.aws.s3.secret_key
,cloud.aws.s3.protocol
,cloud.aws.s3.proxy.host
,cloud.aws.s3.proxy.port
,cloud.aws.s3.proxy.username
,cloud.aws.s3.proxy.password
,cloud.aws.s3.signer
,cloud.aws.s3.read_timeout
,repositories.s3.access_key
,repositories.s3.secret_key
,repositories.s3.endpoint
그리고,repositories.s3.protocol
을 포함한다. 대신,s3.client.CLIENT_NAME.*
아래에 새로 이름 붙여잔 client 설정을 사용하자.The
path_style_access
setting has been removed. The repository will use the appropriate path style access based on the configured endpoint.path_style_access
설정은 제거되었다. repository는 설정된 endpoint에 따라 적절한 path style access를 사용한다.
Azure Repository pluginedit
The container an azure repository is configured with will no longer be created automatically. It must exist before the azure repository is created.
azure repository가 설정된 container는 더 이상 자동으로 생성되지 않는다. azure repository가 생성되기 전에 존재해야 한다.
Global repositories settings you are able to set in elasticsearch config file under
repositories.azure
name space have been removed. This includesrepositories.azure.account
,repositories.azure.container
,repositories.azure.base_path
,repositories.azure.location_mode
,repositories.azure.chunk_size
andrepositories.azure.compress
. You must set those settings per repository instead. Respectivelyaccount
,container
,base_path
,location_mode
,chunk_size
andcompress
. See Azure Repository settings.elasticsearch config 파일에서,
repositories.azure
namespace 아래 설정할 수 있는 global repository 설정이 제거되었다. 여기에는repositories.azure.account
,repositories.azure.container
,repositories.azure.base_path
,repositories.azure.location_mode
,repositories.azure.chunk_size
그리고repositories.azure.compress
을 포함한다. 대신 repository 별로 그것들을 설정해야 한다.account
,container
,base_path
,location_mode
,chunk_size
그리고 `compress`를 각각. Azure Repository settings 을 참고하자.
GCS Repository pluginedit
The
service_account
setting has been removed. A service account json credential file must now be specified in the elasticsearch keystore.service_account
설정은 제거되었다. 이제 service account json credential file은 elasticsearch keystore 에 지정되어야 한다.
EC2 Discovery pluginedit
Specifying ec2 signer type has been removed, including
cloud.aws.signer
andcloud.aws.ec2.signer
.cloud.aws.signer
그리고cloud.aws.ec2.signer
을 포함하여, ec2 signer type을 지정하는 것은 제거되었다.The region setting has been removed. This includes the settings
cloud.aws.region
andcloud.aws.ec2.region
. Instead, specify the full endpoint.resign 설정은 제거되었다. 여기에는
cloud.aws.region
,cloud.aws.ec2.region
을 포함한다. 대신 full endpoint을 지정하자.All
cloud.aws.*
andcloud.aws.ec2.*
settings have been removed. Usediscovery.ec2.*
settings instead.모든
cloud.aws.*
,cloud.aws.ec2.*
설정이 제거되었다. 대신discovery.ec2.*
설정을 사용하자.
edit
Ignoring hidden foldersPrevious versions of Elasticsearch would skip hidden files and directories when scanning the plugins folder. This leniency has been removed.
이전 버전의 Elasticsearch는 plugin folder를 확인할 때 hidden file과 directory를 생략했다. 이 규칙은 제거되었다.
ICU Analysis pluginedit
The icu4j library has been upgraded to 59.1, Indices created in the previous major version will need to be reindexed in order to return correct (and correctly ordered) results, and to take advantage of new characters.
icu4j library가 59.1로 upgrade되었다. 올바른 결과나 순서로 return하고, 새로운 문자를 활요하려면, 이전 major 버전에서 생성된 indices는 다시 index되어야 한다.
Plugins should not construct Environment
instances from Settings
edit
Previously, plugins could construct an Environment
instance from Settings
to discover the path to plugin-specific config files. This will no longer work in all situations as the Settings
object does not carry the necessary information for the config path to be set correctly. Instead, plugins that need to know the config path should have a single constructor that accepts a pair of Settings
and Path
instances, and construct an Environment
using the corresponding constructor on Environment
.
이전에는, plugin이 plugin별 config file의 경로를 찾기 위해, Settings
에서 Environment
instance를 생성했다. Settings
object가 config path가 올바르게 설정되는 데 필요한 정보를 전달하지 않기 때문에, 모든 상황에서 더 이상 동작하지 않는다. 대신 config path를 알아야하는 plugin은 Settings
와 Path
instance 쌍을 받아들이는 단일 constructor를 가져야 하고, Environment
에 해당 constructor를 사용하여Environment
를 생성해야 한다.
'6.x > 8. Breaking Changes' 카테고리의 다른 글
v6.0-16. REST changes (0) | 2017.12.20 |
---|---|
v6.0-15. Reindex changes (0) | 2017.12.20 |
v6.0-13. Percolator changes (0) | 2017.12.20 |
v6.0-12. Packaging changes (0) | 2017.12.20 |
v6.0-11. Mapping changes (0) | 2017.12.20 |