[jira] [Commented] (KYLIN-5604) Open API for adding aggregation group function
[
https://issues.apache.org/jira/browse/KYLIN-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740006#comment-17740006
]
ASF GitHub Bot commented on KYLIN-5604:
---
Mrhs121 commented on code in PR #2133:
URL: https://github.com/apache/kylin/pull/2133#discussion_r1252478543
##
website/docs/restapi/model_api/model_management_api.md:
##
@@ -1178,3 +1178,92 @@ curl -X GET \
```
+### Add aggregate groups
+
+- `PUT http://host:port/kylin/api/index_plans/agg_groups`
+
+- Introduced in: 5.0
+
+- HTTP Header
+
+ - `Accept: application/vnd.apache.kylin-v4-public+json`
+ - `Accept-Language: en`
+ - `Content-Type: application/json;charset=utf-8`
+
+- HTT`P Body: JSON Object`
Review Comment:
修改好了
##
website/docs/restapi/model_api/model_management_api.md:
##
@@ -1178,3 +1178,92 @@ curl -X GET \
```
+### Add aggregate groups
+
+- `PUT http://host:port/kylin/api/index_plans/agg_groups`
+
+- Introduced in: 5.0
+
+- HTTP Header
+
+ - `Accept: application/vnd.apache.kylin-v4-public+json`
+ - `Accept-Language: en`
+ - `Content-Type: application/json;charset=utf-8`
+
+- HTT`P Body: JSON Object`
+
+ - `project` - `required` `string`, project name
+ - `model` - `required` `string`, model name
+ - `aggregation_groups` - `required` `JSON Object[]`, agg group json array,
can add multiple agg groups
+- `dimensions` - `required` `array[string]`, dimension array, must be in
database.table format, and the added dimension must have been added as a
dimension in the model
+- `measures` - `optional` `array[string]`, measure array, the added
measure name is the measure name defined in the model, case-sensitive
+- `mandatory_dims` - `optional` `array[string]`, mandatory dimension
array, the dimensions that must be included in the index generated by the
aggregate group
+- `hierarchy_dims` - `optional` `array[array[string]]`, hierarchy
dimension array, the dimensions that can be optimized according to the
hierarchical relationship in the index generated by the aggregate group, a set
of hierarchy dimensions in an array
+- `joint_dims` - `optional` `array[array[string]]`, joint dimension array,
the dimensions that must also be included in the index generated by the
aggregate group, a set of joint dimensions in an array
+> **NOTICE**： `mandatory_dims` 、`hierarchy_dims` 、`joint_dims` must be in
`dimensions`, and any dimension can only be set once in mandatory dimension,
hierarchy dimension or joint dimension.
+- `dim_cap` - `optional` `int`, Maximum number of dimension
combinations(MDC) for a single aggregate group, positive integer
+ - `global_dim_cap` - `optional` `int`, global MDC in this request, priority
global_dim_cap < dim_cap
+ - `restore_deleted_index` - `optional` `boolean`, When the indexes generated
by the aggregate group have been deleted, whether to generate these indexes
again when adding the aggregate group, the default is false, which means not to
add.
+
+- Curl Request Example
+
+ ```sh
+ curl -X PUT \
+ 'http://localhost:7070/kylin/api/index_plans/agg_groups' \
+ -H 'Accept: application/vnd.apache.kylin-v4-public+json' \
+ -H 'Accept-Language: cn' \
+ -H 'Authorization: Basic QURNSU46S1lMSU4=' \
+ -H 'Content-Type: application/json;charset=utf-8'
+ -d '{"project":"ssb",
+ "model":"testNewName",
+ "aggregation_groups":[
+ {
+"dimensions":[
+"CUSTOMER_DETAILS.IMei",
+"CUSTOMER_DETAILS.REGION",
+"CUSTOMER_DETAILS.BALANCE"
+],
+"measures":[
+"ME2"
+],
+"mandatory_dims":[
+"CUSTOMER_DETAILS.reGION"
+],
+"hierarchy_dims":[
+[
+"CUSTOMER_DETAILS.Imei"
+]
+],
+ "joint_dims":[
+[
+"CUSTOMER_DETAILS.BALANCE"
+]
+],
+"dim_cap": 4
+ }
+ ],
+ "global_dim_cap":3,
+ "restore_deleted_index":false
+ }'
+ ```
+
+- Response Details
+ - code - string, response code, succeed: 000, failed: 999
+ - removed_layouts_size - The number of indexes to delete
+ - added_layouts_size - The number of indexes to add
+ - recovered_layouts_size - The number of deleted indexes in the generated
indexes, when restore_deleted_index = true, these indexes will be added
+
+- Response Details
Review Comment:
修改好了
> Open API for adding aggregation group function
> --
>
> Key: KYLIN-5604
> URL: https://issues.apache.org/jira/browse/KYLIN-5604
> Project: Kylin
> Issue Type: New Feature
> Components: REST Service
>Affects Versions: 5.0-alpha
>Reporter: huangsheng
>Assignee:
[GitHub] [kylin] Mrhs121 commented on a diff in pull request #2133: KYLIN-5604, KYLIN-5598 Documentation
Mrhs121 commented on code in PR #2133:
URL: https://github.com/apache/kylin/pull/2133#discussion_r1252478543
##
website/docs/restapi/model_api/model_management_api.md:
##
@@ -1178,3 +1178,92 @@ curl -X GET \
```
+### Add aggregate groups
+
+- `PUT http://host:port/kylin/api/index_plans/agg_groups`
+
+- Introduced in: 5.0
+
+- HTTP Header
+
+ - `Accept: application/vnd.apache.kylin-v4-public+json`
+ - `Accept-Language: en`
+ - `Content-Type: application/json;charset=utf-8`
+
+- HTT`P Body: JSON Object`
Review Comment:
修改好了
##
website/docs/restapi/model_api/model_management_api.md:
##
@@ -1178,3 +1178,92 @@ curl -X GET \
```
+### Add aggregate groups
+
+- `PUT http://host:port/kylin/api/index_plans/agg_groups`
+
+- Introduced in: 5.0
+
+- HTTP Header
+
+ - `Accept: application/vnd.apache.kylin-v4-public+json`
+ - `Accept-Language: en`
+ - `Content-Type: application/json;charset=utf-8`
+
+- HTT`P Body: JSON Object`
+
+ - `project` - `required` `string`, project name
+ - `model` - `required` `string`, model name
+ - `aggregation_groups` - `required` `JSON Object[]`, agg group json array,
can add multiple agg groups
+- `dimensions` - `required` `array[string]`, dimension array, must be in
database.table format, and the added dimension must have been added as a
dimension in the model
+- `measures` - `optional` `array[string]`, measure array, the added
measure name is the measure name defined in the model, case-sensitive
+- `mandatory_dims` - `optional` `array[string]`, mandatory dimension
array, the dimensions that must be included in the index generated by the
aggregate group
+- `hierarchy_dims` - `optional` `array[array[string]]`, hierarchy
dimension array, the dimensions that can be optimized according to the
hierarchical relationship in the index generated by the aggregate group, a set
of hierarchy dimensions in an array
+- `joint_dims` - `optional` `array[array[string]]`, joint dimension array,
the dimensions that must also be included in the index generated by the
aggregate group, a set of joint dimensions in an array
+> **NOTICE**： `mandatory_dims` 、`hierarchy_dims` 、`joint_dims` must be in
`dimensions`, and any dimension can only be set once in mandatory dimension,
hierarchy dimension or joint dimension.
+- `dim_cap` - `optional` `int`, Maximum number of dimension
combinations(MDC) for a single aggregate group, positive integer
+ - `global_dim_cap` - `optional` `int`, global MDC in this request, priority
global_dim_cap < dim_cap
+ - `restore_deleted_index` - `optional` `boolean`, When the indexes generated
by the aggregate group have been deleted, whether to generate these indexes
again when adding the aggregate group, the default is false, which means not to
add.
+
+- Curl Request Example
+
+ ```sh
+ curl -X PUT \
+ 'http://localhost:7070/kylin/api/index_plans/agg_groups' \
+ -H 'Accept: application/vnd.apache.kylin-v4-public+json' \
+ -H 'Accept-Language: cn' \
+ -H 'Authorization: Basic QURNSU46S1lMSU4=' \
+ -H 'Content-Type: application/json;charset=utf-8'
+ -d '{"project":"ssb",
+ "model":"testNewName",
+ "aggregation_groups":[
+ {
+"dimensions":[
+"CUSTOMER_DETAILS.IMei",
+"CUSTOMER_DETAILS.REGION",
+"CUSTOMER_DETAILS.BALANCE"
+],
+"measures":[
+"ME2"
+],
+"mandatory_dims":[
+"CUSTOMER_DETAILS.reGION"
+],
+"hierarchy_dims":[
+[
+"CUSTOMER_DETAILS.Imei"
+]
+],
+ "joint_dims":[
+[
+"CUSTOMER_DETAILS.BALANCE"
+]
+],
+"dim_cap": 4
+ }
+ ],
+ "global_dim_cap":3,
+ "restore_deleted_index":false
+ }'
+ ```
+
+- Response Details
+ - code - string, response code, succeed: 000, failed: 999
+ - removed_layouts_size - The number of indexes to delete
+ - added_layouts_size - The number of indexes to add
+ - recovered_layouts_size - The number of deleted indexes in the generated
indexes, when restore_deleted_index = true, these indexes will be added
+
+- Response Details
Review Comment:
修改好了
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (KYLIN-5604) Open API for adding aggregation group function
[ https://issues.apache.org/jira/browse/KYLIN-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740003#comment-17740003 ] ASF GitHub Bot commented on KYLIN-5604: --- hit-lacus commented on code in PR #2133: URL: https://github.com/apache/kylin/pull/2133#discussion_r1252474526 ## website/docs/restapi/model_api/model_management_api.md: ## @@ -1178,3 +1178,92 @@ curl -X GET \ ``` +### Add aggregate groups + +- `PUT http://host:port/kylin/api/index_plans/agg_groups` + +- Introduced in: 5.0 + +- HTTP Header + + - `Accept: application/vnd.apache.kylin-v4-public+json` + - `Accept-Language: en` + - `Content-Type: application/json;charset=utf-8` + +- HTT`P Body: JSON Object` Review Comment: 是不是不需要添加反斜线 backtick > Open API for adding aggregation group function > -- > > Key: KYLIN-5604 > URL: https://issues.apache.org/jira/browse/KYLIN-5604 > Project: Kylin > Issue Type: New Feature > Components: REST Service >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Since the latest version of Kylin does not open API interfaces for functions > such as model editing, task management-task deletion, adding detailed > indexes, and adding aggregation groups, etc. > We are currently working on an indicator platform, and we need to use these > interfaces to nest into our own programs for secondary development, so we > hope to open up these APIs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [kylin] hit-lacus commented on a diff in pull request #2133: KYLIN-5604, KYLIN-5598 Documentation
hit-lacus commented on code in PR #2133: URL: https://github.com/apache/kylin/pull/2133#discussion_r1252474526 ## website/docs/restapi/model_api/model_management_api.md: ## @@ -1178,3 +1178,92 @@ curl -X GET \ ``` +### Add aggregate groups + +- `PUT http://host:port/kylin/api/index_plans/agg_groups` + +- Introduced in: 5.0 + +- HTTP Header + + - `Accept: application/vnd.apache.kylin-v4-public+json` + - `Accept-Language: en` + - `Content-Type: application/json;charset=utf-8` + +- HTT`P Body: JSON Object` Review Comment: 是不是不需要添加反斜线 backtick -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (KYLIN-5604) Open API for adding aggregation group function
[
https://issues.apache.org/jira/browse/KYLIN-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740002#comment-17740002
]
ASF GitHub Bot commented on KYLIN-5604:
---
hit-lacus commented on code in PR #2133:
URL: https://github.com/apache/kylin/pull/2133#discussion_r1252474350
##
website/docs/restapi/model_api/model_management_api.md:
##
@@ -1178,3 +1178,92 @@ curl -X GET \
```
+### Add aggregate groups
+
+- `PUT http://host:port/kylin/api/index_plans/agg_groups`
+
+- Introduced in: 5.0
+
+- HTTP Header
+
+ - `Accept: application/vnd.apache.kylin-v4-public+json`
+ - `Accept-Language: en`
+ - `Content-Type: application/json;charset=utf-8`
+
+- HTT`P Body: JSON Object`
+
+ - `project` - `required` `string`, project name
+ - `model` - `required` `string`, model name
+ - `aggregation_groups` - `required` `JSON Object[]`, agg group json array,
can add multiple agg groups
+- `dimensions` - `required` `array[string]`, dimension array, must be in
database.table format, and the added dimension must have been added as a
dimension in the model
+- `measures` - `optional` `array[string]`, measure array, the added
measure name is the measure name defined in the model, case-sensitive
+- `mandatory_dims` - `optional` `array[string]`, mandatory dimension
array, the dimensions that must be included in the index generated by the
aggregate group
+- `hierarchy_dims` - `optional` `array[array[string]]`, hierarchy
dimension array, the dimensions that can be optimized according to the
hierarchical relationship in the index generated by the aggregate group, a set
of hierarchy dimensions in an array
+- `joint_dims` - `optional` `array[array[string]]`, joint dimension array,
the dimensions that must also be included in the index generated by the
aggregate group, a set of joint dimensions in an array
+> **NOTICE**： `mandatory_dims` 、`hierarchy_dims` 、`joint_dims` must be in
`dimensions`, and any dimension can only be set once in mandatory dimension,
hierarchy dimension or joint dimension.
+- `dim_cap` - `optional` `int`, Maximum number of dimension
combinations(MDC) for a single aggregate group, positive integer
+ - `global_dim_cap` - `optional` `int`, global MDC in this request, priority
global_dim_cap < dim_cap
+ - `restore_deleted_index` - `optional` `boolean`, When the indexes generated
by the aggregate group have been deleted, whether to generate these indexes
again when adding the aggregate group, the default is false, which means not to
add.
+
+- Curl Request Example
+
+ ```sh
+ curl -X PUT \
+ 'http://localhost:7070/kylin/api/index_plans/agg_groups' \
+ -H 'Accept: application/vnd.apache.kylin-v4-public+json' \
+ -H 'Accept-Language: cn' \
+ -H 'Authorization: Basic QURNSU46S1lMSU4=' \
+ -H 'Content-Type: application/json;charset=utf-8'
+ -d '{"project":"ssb",
+ "model":"testNewName",
+ "aggregation_groups":[
+ {
+"dimensions":[
+"CUSTOMER_DETAILS.IMei",
+"CUSTOMER_DETAILS.REGION",
+"CUSTOMER_DETAILS.BALANCE"
+],
+"measures":[
+"ME2"
+],
+"mandatory_dims":[
+"CUSTOMER_DETAILS.reGION"
+],
+"hierarchy_dims":[
+[
+"CUSTOMER_DETAILS.Imei"
+]
+],
+ "joint_dims":[
+[
+"CUSTOMER_DETAILS.BALANCE"
+]
+],
+"dim_cap": 4
+ }
+ ],
+ "global_dim_cap":3,
+ "restore_deleted_index":false
+ }'
+ ```
+
+- Response Details
+ - code - string, response code, succeed: 000, failed: 999
+ - removed_layouts_size - The number of indexes to delete
+ - added_layouts_size - The number of indexes to add
+ - recovered_layouts_size - The number of deleted indexes in the generated
indexes, when restore_deleted_index = true, these indexes will be added
+
+- Response Details
Review Comment:
Response Details or Response Example？
> Open API for adding aggregation group function
> --
>
> Key: KYLIN-5604
> URL: https://issues.apache.org/jira/browse/KYLIN-5604
> Project: Kylin
> Issue Type: New Feature
> Components: REST Service
>Affects Versions: 5.0-alpha
>Reporter: huangsheng
>Assignee: huangsheng
>Priority: Major
> Fix For: 5.0-beta
>
>
> Since the latest version of Kylin does not open API interfaces for functions
> such as model editing, task management-task deletion, adding detailed
> indexes, and adding aggregation groups, etc.
> We are currently working on an indicator platform, and we need to use these
> interfaces to nest into our own programs for secondary
[GitHub] [kylin] hit-lacus commented on a diff in pull request #2133: KYLIN-5604, KYLIN-5598 Documentation
hit-lacus commented on code in PR #2133:
URL: https://github.com/apache/kylin/pull/2133#discussion_r1252474350
##
website/docs/restapi/model_api/model_management_api.md:
##
@@ -1178,3 +1178,92 @@ curl -X GET \
```
+### Add aggregate groups
+
+- `PUT http://host:port/kylin/api/index_plans/agg_groups`
+
+- Introduced in: 5.0
+
+- HTTP Header
+
+ - `Accept: application/vnd.apache.kylin-v4-public+json`
+ - `Accept-Language: en`
+ - `Content-Type: application/json;charset=utf-8`
+
+- HTT`P Body: JSON Object`
+
+ - `project` - `required` `string`, project name
+ - `model` - `required` `string`, model name
+ - `aggregation_groups` - `required` `JSON Object[]`, agg group json array,
can add multiple agg groups
+- `dimensions` - `required` `array[string]`, dimension array, must be in
database.table format, and the added dimension must have been added as a
dimension in the model
+- `measures` - `optional` `array[string]`, measure array, the added
measure name is the measure name defined in the model, case-sensitive
+- `mandatory_dims` - `optional` `array[string]`, mandatory dimension
array, the dimensions that must be included in the index generated by the
aggregate group
+- `hierarchy_dims` - `optional` `array[array[string]]`, hierarchy
dimension array, the dimensions that can be optimized according to the
hierarchical relationship in the index generated by the aggregate group, a set
of hierarchy dimensions in an array
+- `joint_dims` - `optional` `array[array[string]]`, joint dimension array,
the dimensions that must also be included in the index generated by the
aggregate group, a set of joint dimensions in an array
+> **NOTICE**： `mandatory_dims` 、`hierarchy_dims` 、`joint_dims` must be in
`dimensions`, and any dimension can only be set once in mandatory dimension,
hierarchy dimension or joint dimension.
+- `dim_cap` - `optional` `int`, Maximum number of dimension
combinations(MDC) for a single aggregate group, positive integer
+ - `global_dim_cap` - `optional` `int`, global MDC in this request, priority
global_dim_cap < dim_cap
+ - `restore_deleted_index` - `optional` `boolean`, When the indexes generated
by the aggregate group have been deleted, whether to generate these indexes
again when adding the aggregate group, the default is false, which means not to
add.
+
+- Curl Request Example
+
+ ```sh
+ curl -X PUT \
+ 'http://localhost:7070/kylin/api/index_plans/agg_groups' \
+ -H 'Accept: application/vnd.apache.kylin-v4-public+json' \
+ -H 'Accept-Language: cn' \
+ -H 'Authorization: Basic QURNSU46S1lMSU4=' \
+ -H 'Content-Type: application/json;charset=utf-8'
+ -d '{"project":"ssb",
+ "model":"testNewName",
+ "aggregation_groups":[
+ {
+"dimensions":[
+"CUSTOMER_DETAILS.IMei",
+"CUSTOMER_DETAILS.REGION",
+"CUSTOMER_DETAILS.BALANCE"
+],
+"measures":[
+"ME2"
+],
+"mandatory_dims":[
+"CUSTOMER_DETAILS.reGION"
+],
+"hierarchy_dims":[
+[
+"CUSTOMER_DETAILS.Imei"
+]
+],
+ "joint_dims":[
+[
+"CUSTOMER_DETAILS.BALANCE"
+]
+],
+"dim_cap": 4
+ }
+ ],
+ "global_dim_cap":3,
+ "restore_deleted_index":false
+ }'
+ ```
+
+- Response Details
+ - code - string, response code, succeed: 000, failed: 999
+ - removed_layouts_size - The number of indexes to delete
+ - added_layouts_size - The number of indexes to add
+ - recovered_layouts_size - The number of deleted indexes in the generated
indexes, when restore_deleted_index = true, these indexes will be added
+
+- Response Details
Review Comment:
Response Details or Response Example？
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (KYLIN-5604) Open API for adding aggregation group function
[ https://issues.apache.org/jira/browse/KYLIN-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739873#comment-17739873 ] ASF GitHub Bot commented on KYLIN-5604: --- Mrhs121 opened a new pull request, #2133: URL: https://github.com/apache/kylin/pull/2133 ## Proposed changes Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [x] Branch **kylin5** for v5.x ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] Documentation Update (if none of the other choices apply) ## Checklist _Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._ - [x] I have created an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [ ] Commit messages in my PR start with the related jira ID, like "KYLIN- Make Kylin project open-source" - [ ] Compiling and unit tests pass locally with my changes - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc... > Open API for adding aggregation group function > -- > > Key: KYLIN-5604 > URL: https://issues.apache.org/jira/browse/KYLIN-5604 > Project: Kylin > Issue Type: New Feature > Components: REST Service >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Since the latest version of Kylin does not open API interfaces for functions > such as model editing, task management-task deletion, adding detailed > indexes, and adding aggregation groups, etc. > We are currently working on an indicator platform, and we need to use these > interfaces to nest into our own programs for secondary development, so we > hope to open up these APIs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [kylin] Mrhs121 opened a new pull request, #2133: KYLIN-5604, KYLIN-5598 Documentation
Mrhs121 opened a new pull request, #2133: URL: https://github.com/apache/kylin/pull/2133 ## Proposed changes Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [x] Branch **kylin5** for v5.x ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] Documentation Update (if none of the other choices apply) ## Checklist _Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._ - [x] I have created an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [ ] Commit messages in my PR start with the related jira ID, like "KYLIN- Make Kylin project open-source" - [ ] Compiling and unit tests pass locally with my changes - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (KYLIN-5610) Should automatically copy some of the necessary jars from kylin/server/jar into kylin/spark/jars
[ https://issues.apache.org/jira/browse/KYLIN-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5610: -- Description: Such as, when soft-affinity is enabled, spark depends on some special jars which are customized by kylin. Therefore, we need to copy these jars from kylin/server/jar to spark/jars automatically after downloading spark. (was: Such as, when soft-affinity is enabled, spark depends on some special jars. Therefore, we need to copy these jars from kylin/server/jar to spark/jars automatically after downloading spark.) > Should automatically copy some of the necessary jars from kylin/server/jar > into kylin/spark/jars > > > Key: KYLIN-5610 > URL: https://issues.apache.org/jira/browse/KYLIN-5610 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Such as, when soft-affinity is enabled, spark depends on some special jars > which are customized by kylin. Therefore, we need to copy these jars from > kylin/server/jar to spark/jars automatically after downloading spark. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5610) Should automatically copy some of the necessary jars from kylin/server/jar into kylin/spark/jars
[ https://issues.apache.org/jira/browse/KYLIN-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5610: -- Description: Such as, when soft-affinity is enabled, spark depends on some special jars. Therefore, we need to copy these jars from kylin/server/jar to spark/jars automatically after downloading spark. (was: Such as, when soft-affinity is enabled, spark depends on some special jar packages. Therefore, we need to copy these jar packages to spark/jars automatically after downloading spark.) > Should automatically copy some of the necessary jars from kylin/server/jar > into kylin/spark/jars > > > Key: KYLIN-5610 > URL: https://issues.apache.org/jira/browse/KYLIN-5610 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Such as, when soft-affinity is enabled, spark depends on some special jars. > Therefore, we need to copy these jars from kylin/server/jar to spark/jars > automatically after downloading spark. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5599) In the scenario where there are many users in the user group, the performance of assigning users to the user group is extremely poor
[ https://issues.apache.org/jira/browse/KYLIN-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5599: -- Fix Version/s: (was: 5.0-alpha) > In the scenario where there are many users in the user group, the performance > of assigning users to the user group is extremely poor > > > Key: KYLIN-5599 > URL: https://issues.apache.org/jira/browse/KYLIN-5599 > Project: Kylin > Issue Type: New Feature > Components: REST Service >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Currently, in my development environment, there are 2w+ users in a user > group, and 1w+ users in the production environment. In the scenario where > there are many users in the user group, the performance of assigning users to > the user group is extremely poor. > So I want to ensure that when the number of users in the user group is more > than 20,000, assign users to the user group to respond within a reasonable > time (such as 10 seconds) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5601) V2 dictionary workaround fixes
[ https://issues.apache.org/jira/browse/KYLIN-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5601: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > V2 dictionary workaround fixes > -- > > Key: KYLIN-5601 > URL: https://issues.apache.org/jira/browse/KYLIN-5601 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > In some scenarios, AQE optimizes the step of writing the dictionary from > repartition in the execution plan, skips the encoding of some partitioned > dictionaries, and there is no abnormal prompt in the task status, which > eventually leads to an error in the calculation of the count distinct metric. > So consider turning off AQE during dictionary construction -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5598) Support Kylin to authenticate zk to use username + password (no kerberos required)
[ https://issues.apache.org/jira/browse/KYLIN-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5598: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > Support Kylin to authenticate zk to use username + password (no kerberos > required) > -- > > Key: KYLIN-5598 > URL: https://issues.apache.org/jira/browse/KYLIN-5598 > Project: Kylin > Issue Type: New Feature > Components: Environment >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > Attachments: image-2023-07-03-13-51-08-810.png, > image-2023-07-03-13-55-52-102.png, image-2023-07-03-13-55-52-195.png, > image-2023-07-03-13-55-52-256.png > > > Support Kylin to authenticate zk to use username + password (kerberos is not > required). In some user-defined scenarios, there is no kerberos, but the user > name and password are used to authenticate zk. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5598) Support Kylin to authenticate zk to use username + password (no kerberos required)
[ https://issues.apache.org/jira/browse/KYLIN-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5598: -- Fix Version/s: (was: 5.0-beta) > Support Kylin to authenticate zk to use username + password (no kerberos > required) > -- > > Key: KYLIN-5598 > URL: https://issues.apache.org/jira/browse/KYLIN-5598 > Project: Kylin > Issue Type: New Feature > Components: Environment >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-alpha > > Attachments: image-2023-07-03-13-51-08-810.png, > image-2023-07-03-13-55-52-102.png, image-2023-07-03-13-55-52-195.png, > image-2023-07-03-13-55-52-256.png > > > Support Kylin to authenticate zk to use username + password (kerberos is not > required). In some user-defined scenarios, there is no kerberos, but the user > name and password are used to authenticate zk. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5602) Added logs related to Segment Pruning for derived dimension queries
[ https://issues.apache.org/jira/browse/KYLIN-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5602: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > Added logs related to Segment Pruning for derived dimension queries > > > Key: KYLIN-5602 > URL: https://issues.apache.org/jira/browse/KYLIN-5602 > Project: Kylin > Issue Type: New Feature > Components: Query Engine >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Supplement Derived segment pruning related logs > # Query whether Derived Segment Pruning is used, and filter a few > # Add Metric to quantify the effect of Derived Segment Pruning, such as: > counting the filtered segment size and counting the time of Bloom Filter -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5606) [Aggregation Group API] The required item aggregate_group is not passed, and the prompt information is unclear
[ https://issues.apache.org/jira/browse/KYLIN-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5606: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > [Aggregation Group API] The required item aggregate_group is not passed, and > the prompt information is unclear > -- > > Key: KYLIN-5606 > URL: https://issues.apache.org/jira/browse/KYLIN-5606 > Project: Kylin > Issue Type: Bug > Components: REST Service >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > Attachments: image-2023-07-03-19-29-42-051.png > > > [Aggregation Group API] The required item aggregate_group is not passed, and > the prompt information is unclear -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5603) After the V2 dictionary is automatically upgraded to the V3 dictionary, the dictionary data is abnormal, resulting in incorrect query results
[ https://issues.apache.org/jira/browse/KYLIN-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5603: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > After the V2 dictionary is automatically upgraded to the V3 dictionary, the > dictionary data is abnormal, resulting in incorrect query results > - > > Key: KYLIN-5603 > URL: https://issues.apache.org/jira/browse/KYLIN-5603 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > Attachments: image-2023-07-03-17-23-36-745.png, > image-2023-07-03-17-28-10-272.png, image-2023-07-03-17-30-18-755.png > > > After v2 upgrades the v3 dictionary, if v2 and v3 are mixed, the query result > is incorrect > Root Cause > The project opens the v3 dictionary construction, but when the v3 dictionary > construction reads the v2 dictionary, the db name is not included in the > path, so the v2 dictionary will not be read, causing the v2 upgrade and the > v3 dictionary conversion step to be skipped directly, and v3 is equivalent to > recoding. Therefore, the v2 upgrade v3 dictionary must not be available, and > the encoding is disordered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5607) When querying with high concurrency, the query may report an error (the thread is not safe when ACL permission multi-threaded concurrent access)
[ https://issues.apache.org/jira/browse/KYLIN-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5607: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > When querying with high concurrency, the query may report an error (the > thread is not safe when ACL permission multi-threaded concurrent access) > > > Key: KYLIN-5607 > URL: https://issues.apache.org/jira/browse/KYLIN-5607 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > Attachments: image-2023-07-03-19-47-53-917.png > > > ACL records are taken out of the cache, and the internal array is modified by > sorting in the init method. Since the metadata in Kylin is shared, there will > be multi-threaded access problems, so there will be concurrent modification > problems here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5600) LDAP DN is not case sensitive, resulting in user login failure
[ https://issues.apache.org/jira/browse/KYLIN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5600: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > LDAP DN is not case sensitive, resulting in user login failure > -- > > Key: KYLIN-5600 > URL: https://issues.apache.org/jira/browse/KYLIN-5600 > Project: Kylin > Issue Type: Bug > Components: REST Service, Security >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > Attachments: image-1.png, image-2023-07-03-14-33-19-505.png, > image-2023-07-03-14-33-56-559.png, image.png > > > In some user scenarios, uppercase and lowercase logins to LDAP fail. > Root Cause： > When all users are obtained from ldapUserService in the code, the attribute > names in the recorded dn contain uppercase letters, but the DN attribute > names passed in by customers when they log in to ldap are lowercase, > resulting in inconsistent capitalization and login failure. Customers here CN > =xxx,DU=xxx,DC=xxx, but ldap here is cn=xxx,du=xxx,dc=xxx > A point where later maintenance can be optimized: > When troubleshooting LDAP problems, there are often strange problems that the > user names cannot be matched. It is very laborious to troubleshoot. You need > to add this information to the log instead of printing it all the time. You > can consider printing it after polling for a number of times, and printing it > when it is loaded for the first time. and so on > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5605) When starting kylin in the FI environment, if the Kerberos configuration KAP_KERBEROS_ENABLED is empty, the spark jar replacement will not be performed, resulting in star
[ https://issues.apache.org/jira/browse/KYLIN-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5605: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > When starting kylin in the FI environment, if the Kerberos configuration > KAP_KERBEROS_ENABLED is empty, the spark jar replacement will not be > performed, resulting in startup failure > - > > Key: KYLIN-5605 > URL: https://issues.apache.org/jira/browse/KYLIN-5605 > Project: Kylin > Issue Type: Bug > Components: Environment >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > Attachments: image-2023-07-03-19-19-11-529.png, > image-2023-07-03-19-20-11-766.png, image-2023-07-03-19-21-09-252.png > > > When starting kylin in the FI environment, if the Kerberos configuration > KAP_KERBEROS_ENABLED is empty, the jar package replacement will not be > performed, resulting in startup failure -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5604) Open API for adding aggregation group function
[ https://issues.apache.org/jira/browse/KYLIN-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5604: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > Open API for adding aggregation group function > -- > > Key: KYLIN-5604 > URL: https://issues.apache.org/jira/browse/KYLIN-5604 > Project: Kylin > Issue Type: New Feature > Components: REST Service >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Since the latest version of Kylin does not open API interfaces for functions > such as model editing, task management-task deletion, adding detailed > indexes, and adding aggregation groups, etc. > We are currently working on an indicator platform, and we need to use these > interfaces to nest into our own programs for secondary development, so we > hope to open up these APIs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5608) [Aggregation Group API] Indexes added via the Aggregate Group API, the order of dimensions displayed on the page is inconsistent with the order passed in by the api
[ https://issues.apache.org/jira/browse/KYLIN-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5608: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > [Aggregation Group API] Indexes added via the Aggregate Group API, the order > of dimensions displayed on the page is inconsistent with the order passed in > by the api > > > Key: KYLIN-5608 > URL: https://issues.apache.org/jira/browse/KYLIN-5608 > Project: Kylin > Issue Type: Bug > Components: REST Service >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > [Aggregation Group API] Calling the newly added index of the aggregation > group API, the order of dimensions displayed on the page is inconsistent with > the order passed in by the api -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5610) Should automatically copy some of the necessary jars from kylin/server/jar into kylin/spark/jars
[ https://issues.apache.org/jira/browse/KYLIN-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5610: -- Description: Such as, when soft-affinity is enabled, spark depends on some special jar packages. Therefore, we need to copy these jar packages to spark/jars automatically after downloading spark. (was: When soft-affinity is enabled, spark depends on some special jar packages. Therefore, we need to copy these jar packages to spark/jars automatically after downloading spark) > Should automatically copy some of the necessary jars from kylin/server/jar > into kylin/spark/jars > > > Key: KYLIN-5610 > URL: https://issues.apache.org/jira/browse/KYLIN-5610 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Such as, when soft-affinity is enabled, spark depends on some special jar > packages. Therefore, we need to copy these jar packages to spark/jars > automatically after downloading spark. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5609) Fix security vulnerabilities, upgrade spark version to 3.2.0-kylin-4.6.8.0
[ https://issues.apache.org/jira/browse/KYLIN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangsheng updated KYLIN-5609: -- Fix Version/s: 5.0-beta (was: 5.0-alpha) > Fix security vulnerabilities, upgrade spark version to 3.2.0-kylin-4.6.8.0 > --- > > Key: KYLIN-5609 > URL: https://issues.apache.org/jira/browse/KYLIN-5609 > Project: Kylin > Issue Type: Bug > Components: Spark Engine >Affects Versions: 5.0-alpha >Reporter: huangsheng >Assignee: huangsheng >Priority: Major > Fix For: 5.0-beta > > > Due to the CVE-2023-24998 security vulnerability in spark > 3.2.0-kylin-4.6.7.0, upgrade spark to 3.2.0-kylin-4.6.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5597) When the /etc/hosts file of the Kylin node does not configure the IP corresponding to the cluster domain name in the hadoop conf configuration file, Kylin will fail to st
[
https://issues.apache.org/jira/browse/KYLIN-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huangsheng updated KYLIN-5597:
--
Fix Version/s: 5.0-beta
(was: 5.0-alpha)
> When the /etc/hosts file of the Kylin node does not configure the IP
> corresponding to the cluster domain name in the hadoop conf configuration
> file, Kylin will fail to start
> -
>
> Key: KYLIN-5597
> URL: https://issues.apache.org/jira/browse/KYLIN-5597
> Project: Kylin
> Issue Type: Bug
> Components: Environment , Security
>Affects Versions: 5.0-alpha
>Reporter: huangsheng
>Assignee: huangsheng
>Priority: Major
> Fix For: 5.0-beta
>
>
> If the IP corresponding to the cluster domain name in the hadoop conf
> configuration file is not configured in the /etc/hosts file of the newly
> added KE node, the command
> {code:java}
> get-properties.sh kylin.kerberos.enabled{code}
> will fail when the service starts, and throw java.net.UnknownHostException
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (KYLIN-5610) Should automatically copy some of the necessary jars from kylin/server/jar into kylin/spark/jars
huangsheng created KYLIN-5610: - Summary: Should automatically copy some of the necessary jars from kylin/server/jar into kylin/spark/jars Key: KYLIN-5610 URL: https://issues.apache.org/jira/browse/KYLIN-5610 Project: Kylin Issue Type: Bug Components: Tools, Build and Test Affects Versions: 5.0-alpha Reporter: huangsheng Assignee: huangsheng Fix For: 5.0-beta When soft-affinity is enabled, spark depends on some special jar packages. Therefore, we need to copy these jar packages to spark/jars automatically after downloading spark -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5597) When the /etc/hosts file of the Kylin node does not configure the IP corresponding to the cluster domain name in the hadoop conf configuration file, Kylin will fail to
[
https://issues.apache.org/jira/browse/KYLIN-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739826#comment-17739826
]
ASF GitHub Bot commented on KYLIN-5597:
---
Mrhs121 opened a new pull request, #2132:
URL: https://github.com/apache/kylin/pull/2132
## Proposed changes
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug or
resolves a feature request, be sure to link to that issue.
## Branch to commit
- [ ] Branch **kylin3** for v2.x to v3.x
- [ ] Branch **kylin4** for v4.x
- [x] Branch **kylin5** for v5.x
## Types of changes
What types of changes does your code introduce to Kylin?
_Put an `x` in the boxes that apply_
- [x] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation Update (if none of the other choices apply)
## Checklist
_Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look for
before merging your code._
- [x] I have created an issue on [Kylin's
jira](https://issues.apache.org/jira/browse/KYLIN), and have described the
bug/feature there in detail
- [x] Commit messages in my PR start with the related jira ID, like
"KYLIN- Make Kylin project open-source"
- [x] Compiling and unit tests pass locally with my changes
- [x] I have added tests that prove my fix is effective or that my feature
works
- [x] I have added necessary documentation (if appropriate)
- [x] Any dependent changes have been merged
## Further comments
If this is a relatively large or complex change, kick off the discussion at
u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the
solution you did and what alternatives you considered, etc...
> When the /etc/hosts file of the Kylin node does not configure the IP
> corresponding to the cluster domain name in the hadoop conf configuration
> file, Kylin will fail to start
> -
>
> Key: KYLIN-5597
> URL: https://issues.apache.org/jira/browse/KYLIN-5597
> Project: Kylin
> Issue Type: Bug
> Components: Environment , Security
>Affects Versions: 5.0-alpha
>Reporter: huangsheng
>Assignee: huangsheng
>Priority: Major
> Fix For: 5.0-alpha
>
>
> If the IP corresponding to the cluster domain name in the hadoop conf
> configuration file is not configured in the /etc/hosts file of the newly
> added KE node, the command
> {code:java}
> get-properties.sh kylin.kerberos.enabled{code}
> will fail when the service starts, and throw java.net.UnknownHostException
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [kylin] Mrhs121 opened a new pull request, #2132: KYLIN-5597~5609 Batch ISSUE
Mrhs121 opened a new pull request, #2132: URL: https://github.com/apache/kylin/pull/2132 ## Proposed changes Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [x] Branch **kylin5** for v5.x ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [x] Bugfix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation Update (if none of the other choices apply) ## Checklist _Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._ - [x] I have created an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [x] Commit messages in my PR start with the related jira ID, like "KYLIN- Make Kylin project open-source" - [x] Compiling and unit tests pass locally with my changes - [x] I have added tests that prove my fix is effective or that my feature works - [x] I have added necessary documentation (if appropriate) - [x] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
