[jira] [Updated] (COMDEV-498) Improving End-to-End Test Infrastructure of Apache StreamPipes
[ https://issues.apache.org/jira/browse/COMDEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated COMDEV-498: Labels: StreamPipes full-time gsoc gsoc2023 mentor (was: full-time gsoc gsoc2023 mentor streampipes) > Improving End-to-End Test Infrastructure of Apache StreamPipes > -- > > Key: COMDEV-498 > URL: https://issues.apache.org/jira/browse/COMDEV-498 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Philipp Zehnder >Priority: Major > Labels: StreamPipes, full-time, gsoc, gsoc2023, mentor > > h3. Apache StreamPipes > Apache StreamPipes (incubating) is a self-service (Industrial) IoT toolbox to > enable non-technical users to connect, analyze and explore IoT data streams. > StreamPipes offers several modules including StreamPipes Connect to easily > connect data from industrial IoT sources, the Pipeline Editor to quickly > create processing pipelines and several visualization modules for live and > historic data exploration. Under the hood, StreamPipes utilizes an > event-driven microservice paradigm of standalone, so-called analytics > microservices making the system easy to extend for individual needs. > h3. Background > StreamPipes has grown significantly over the past few years, with new > features and contributors joining the project. However, as the project > continues to evolve, e2e test coverage must also be improved to ensure that > all features remain functional. Modern frameworks, such as Cypress, make it > quite easy and fun to automatically test even complex application > functionalities. As StreamPipes approaches its 1.0 release, it is important > to improve e2e testing to ensure the robustness of the project and its use in > real-world scenarios. > h3. Tasks > - [ ] Write e2e tests using Cypress to cover most functionalities and user > interface components of StreamPipes. > - [ ] Add more complex testing scenarios to ensure the reliability and > robustness of StreamPipes in real-world use cases (e.g. automated tests for > version updates) > - [ ] Add e2e tests for the new Python client to ensure its integration with > the main system and its functionalities ([#774 | > [https://github.com/apache/streampipes/issues/774|https://github.com/apache/streampipes/issues/774]]]) > > - [ ] Document the testing infrastructure and the testing approach to allow > for easy maintenance and future contributions. > h3. ❗ Important Note ❗ > Do not create any account on behalf of Apache StreamPipes in Cypress or using > the name of Apache StreamPipes for any account creation. Your mentor will > take care of it. > h3. Relevant Skills > - Familiarity with testing frameworks, such as Cypress or Selenium > - Experience with TypeScript or Java > - Basic knowledge of Angular is helpful > - Familiarity with Docker and containerization is a plus > h3. Learning Material > * [Cypress docs > |https://docs.cypress.io/guides/getting-started/installing-cypress] > * [Learn Cypress|https://learn.cypress.io/] > * [Angular docs |https://angular.io/docs] > *References* > You can find our corresponding issue on GitHub [here > |https://github.com/apache/streampipes/issues/1371] > h3. *Name and Contact Information* > Name: Philipp Zehnder > email: zehnder[at]apache.org > community: dev[at]streampipes.apache.org > website: [https://streampipes.apache.org/] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-504) Apache ShenYu Gsoc 2023 - Design and implement shenyu ingress-controller in k8s
[ https://issues.apache.org/jira/browse/COMDEV-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated COMDEV-504: Labels: ShenYu full-time gsoc gsoc2023 (was: full-time gsoc gsoc2023) > Apache ShenYu Gsoc 2023 - Design and implement shenyu ingress-controller in > k8s > --- > > Key: COMDEV-504 > URL: https://issues.apache.org/jira/browse/COMDEV-504 > Project: Community Development > Issue Type: New Feature > Components: Comdev, GSoC/Mentoring ideas >Reporter: Yu Xiao >Priority: Major > Labels: ShenYu, full-time, gsoc, gsoc2023 > > h2. Background > Apache ShenYu is a Java native API Gateway for service proxy, protocol > conversion and API governance. Currently, ShenYu has good usability and > performance in microservice scenarios. However, ShenYu's support for > Kubernetes is still relatively weak. > h2. Tasks > 1. Discuss with mentors, and complete the requirements design and technical > design of shenyu-ingress-controller. > 2. Complete the initial version of shenyu-ingress-controller, implement the > reconcile of k8s ingress api, and make ShenYu as the ingress gateway of k8s. > 3. Complete the ci test of shenyu-ingress-controller, verify the correctness > of the code. > h2. Relevant Skills > 1. Know the use of Apache ShenYu > 2. Familiar with Java and Golang > 3. Familiar with Kubernetes and can use java or golang to develop Kubernetes > Controller > h2. Description > Issues ： https://github.com/apache/shenyu/issues/4438 > website ： https://shenyu.apache.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-489) Apache ShardingSphere: Enhance SQLNodeConverterEngine to support more MySQL SQL statements
[
https://issues.apache.org/jira/browse/COMDEV-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697050#comment-17697050
]
Gael Yimen Yimga commented on COMDEV-489:
-
Hello Mentors,
I started looking into this ticket and I have been investigating and debugging
the *select_char* operator. Here is the beginning of my
[thoughts|https://github.com/apache/shardingsphere/discussions/24097#discussioncomment-4996681].
I would like to give a proposal on how to solve the problem.
My findings are the following :
* I notice that for most of the MySQL functions, they are parsed as
`*ExpressionSegment*`.
* That `*ExpressionSegment*` is converted into `*FunctionSegment*`.
* But the `*FunctionSegment*` that is supposed to have the parameters set does
not have it.
The solution could be to find a mechanism to populate the parameters of
`*FunctionSegment*` as a list of `*ExpressionSegment*`. By doing so the
solution can fix al test case for the MySQL functions.
Please let me know what you think about.
> Apache ShardingSphere: Enhance SQLNodeConverterEngine to support more MySQL
> SQL statements
> --
>
> Key: COMDEV-489
> URL: https://issues.apache.org/jira/browse/COMDEV-489
> Project: Community Development
> Issue Type: Improvement
> Components: GSoC/Mentoring ideas
>Reporter: Zhengqiang Duan
>Priority: Major
> Labels: Mentor, ShardingSphere, gsoc2023
>
> h2. Apache ShardingSphere
> Apache ShardingSphere is positioned as a Database Plus, and aims at building
> a standard layer and ecosystem above heterogeneous databases. It focuses on
> how to reuse existing databases and their respective upper layer, rather than
> creating a new database. The goal is to minimize or eliminate the challenges
> caused by underlying databases fragmentation.
> {*}Page{*}:
> [https://shardingsphere.apache.org|https://shardingsphere.apache.org/]
> {*}Github{*}: [https://github.com/apache/shardingsphere]
> h2. Background
> The ShardingSphere SQL federation engine provides support for complex SQL
> statements, and it can well support cross-database join queries, subqueries,
> aggregation queries and other statements. An important part of SQL federation
> engine is to convert the SQL statement parsed by ShardingSphere into SqlNode,
> so that Calcite can be used to implement SQL optimization and federated query.
> h2. Task
> This issue is to solve the MySQL exception that occurs during
> SQLNodeConverterEngine conversion. The specific case list is as follows.
> * select_char
> * select_extract
> * select_from_dual
> * select_from_with_table
> * select_group_by_with_having_and_window
> * select_not_between_with_single_table
> * select_not_in_with_single_table
> * select_substring
> * select_trim
> * select_weight_string
> * select_where_with_bit_expr_with_ampersand
> * select_where_with_bit_expr_with_caret
> * select_where_with_bit_expr_with_div
> * select_where_with_bit_expr_with_minus_interval
> * select_where_with_bit_expr_with_mod
> * select_where_with_bit_expr_with_mod_sign
> * select_where_with_bit_expr_with_plus_interval
> * select_where_with_bit_expr_with_signed_left_shift
> * select_where_with_bit_expr_with_signed_right_shift
> * select_where_with_bit_expr_with_vertical_bar
> * select_where_with_boolean_primary_with_comparison_subquery
> * select_where_with_boolean_primary_with_is
> * select_where_with_boolean_primary_with_is_not
> * select_where_with_boolean_primary_with_null_safe
> * select_where_with_expr_with_and_sign
> * select_where_with_expr_with_is
> * select_where_with_expr_with_is_not
> * select_where_with_expr_with_not
> * select_where_with_expr_with_not_sign
> * select_where_with_expr_with_or_sign
> * select_where_with_expr_with_xor
> * select_where_with_predicate_with_in_subquery
> * select_where_with_predicate_with_regexp
> * select_where_with_predicate_with_sounds_like
> * select_where_with_simple_expr_with_collate
> * select_where_with_simple_expr_with_match
> * select_where_with_simple_expr_with_not
> * select_where_with_simple_expr_with_odbc_escape_syntax
> * select_where_with_simple_expr_with_row
> * select_where_with_simple_expr_with_tilde
> * select_where_with_simple_expr_with_variable
> * select_window_function
> * select_with_assignment_operator
> * select_with_assignment_operator_and_keyword
> * select_with_case_expression
> * select_with_collate_with_marker
> * select_with_date_format_function
> * select_with_exists_sub_query_with_project
> * select_with_function_name
> * select_with_json_value_return_type
> * select_with_match_against
> * select_with_regexp
> * select_with_schema_name_in_column_projection
> * select_with_schema_name_in_shorthand_projection
> *
[GitHub] [comdev-site] rbowen opened a new pull request, #86: Clarify who can propose a new committer or PMC member
rbowen opened a new pull request, #86: URL: https://github.com/apache/comdev-site/pull/86 Some PMCs seem to think that only the PMC chair has the right to propose new committers or PMC members. Clarify that ANY PMC member may do so. The PMC chair is NOT the project lead. They're the secretary. -- 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: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-489) Apache ShardingSphere: Enhance SQLNodeConverterEngine to support more MySQL SQL statements
[
https://issues.apache.org/jira/browse/COMDEV-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697195#comment-17697195
]
Zhengqiang Duan commented on COMDEV-489:
Hi [~yimengael], your solution idea is correct, you can try to solve it. In
addition to the tasks above on jira, there is a list of other unsupported tasks
that you can try before the event.
You can refer to the SQLNodeConverterEngineIT class and delete the
SUPPORTED_SQL_CASE_IDS parameter, so that you can run all the cases. At this
time, there will be a lot of SQL that does not support conversion. These are
our goals. This PR is a good example -
[#13891|https://github.com/apache/shardingsphere/pull/13891].
> Apache ShardingSphere: Enhance SQLNodeConverterEngine to support more MySQL
> SQL statements
> --
>
> Key: COMDEV-489
> URL: https://issues.apache.org/jira/browse/COMDEV-489
> Project: Community Development
> Issue Type: Improvement
> Components: GSoC/Mentoring ideas
>Reporter: Zhengqiang Duan
>Priority: Major
> Labels: Mentor, ShardingSphere, gsoc2023
>
> h2. Apache ShardingSphere
> Apache ShardingSphere is positioned as a Database Plus, and aims at building
> a standard layer and ecosystem above heterogeneous databases. It focuses on
> how to reuse existing databases and their respective upper layer, rather than
> creating a new database. The goal is to minimize or eliminate the challenges
> caused by underlying databases fragmentation.
> {*}Page{*}:
> [https://shardingsphere.apache.org|https://shardingsphere.apache.org/]
> {*}Github{*}: [https://github.com/apache/shardingsphere]
> h2. Background
> The ShardingSphere SQL federation engine provides support for complex SQL
> statements, and it can well support cross-database join queries, subqueries,
> aggregation queries and other statements. An important part of SQL federation
> engine is to convert the SQL statement parsed by ShardingSphere into SqlNode,
> so that Calcite can be used to implement SQL optimization and federated query.
> h2. Task
> This issue is to solve the MySQL exception that occurs during
> SQLNodeConverterEngine conversion. The specific case list is as follows.
> * select_char
> * select_extract
> * select_from_dual
> * select_from_with_table
> * select_group_by_with_having_and_window
> * select_not_between_with_single_table
> * select_not_in_with_single_table
> * select_substring
> * select_trim
> * select_weight_string
> * select_where_with_bit_expr_with_ampersand
> * select_where_with_bit_expr_with_caret
> * select_where_with_bit_expr_with_div
> * select_where_with_bit_expr_with_minus_interval
> * select_where_with_bit_expr_with_mod
> * select_where_with_bit_expr_with_mod_sign
> * select_where_with_bit_expr_with_plus_interval
> * select_where_with_bit_expr_with_signed_left_shift
> * select_where_with_bit_expr_with_signed_right_shift
> * select_where_with_bit_expr_with_vertical_bar
> * select_where_with_boolean_primary_with_comparison_subquery
> * select_where_with_boolean_primary_with_is
> * select_where_with_boolean_primary_with_is_not
> * select_where_with_boolean_primary_with_null_safe
> * select_where_with_expr_with_and_sign
> * select_where_with_expr_with_is
> * select_where_with_expr_with_is_not
> * select_where_with_expr_with_not
> * select_where_with_expr_with_not_sign
> * select_where_with_expr_with_or_sign
> * select_where_with_expr_with_xor
> * select_where_with_predicate_with_in_subquery
> * select_where_with_predicate_with_regexp
> * select_where_with_predicate_with_sounds_like
> * select_where_with_simple_expr_with_collate
> * select_where_with_simple_expr_with_match
> * select_where_with_simple_expr_with_not
> * select_where_with_simple_expr_with_odbc_escape_syntax
> * select_where_with_simple_expr_with_row
> * select_where_with_simple_expr_with_tilde
> * select_where_with_simple_expr_with_variable
> * select_window_function
> * select_with_assignment_operator
> * select_with_assignment_operator_and_keyword
> * select_with_case_expression
> * select_with_collate_with_marker
> * select_with_date_format_function
> * select_with_exists_sub_query_with_project
> * select_with_function_name
> * select_with_json_value_return_type
> * select_with_match_against
> * select_with_regexp
> * select_with_schema_name_in_column_projection
> * select_with_schema_name_in_shorthand_projection
> * select_with_spatial_function
> * select_with_trim_expr
> * select_with_trim_expr_from_expr
> You need to compare the difference between actual and expected, and then
> correct the logic in SQLNodeConverterEngine so that actual can be consistent
> with expected.
> After you make changes, remember to add case to SUPPORTED_SQ
[GitHub] [comdev-site] clr-apache commented on pull request #86: Clarify who can propose a new committer or PMC member
clr-apache commented on PR #86: URL: https://github.com/apache/comdev-site/pull/86#issuecomment-1457395371 LGTM -- 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: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-505) GSoC: Make RocketMQ support higher versions of Java
Yangkun Ai created COMDEV-505:
-
Summary: GSoC: Make RocketMQ support higher versions of Java
Key: COMDEV-505
URL: https://issues.apache.org/jira/browse/COMDEV-505
Project: Community Development
Issue Type: Task
Reporter: Yangkun Ai
h2. Apache RocketMQ
Apache RocketMQ is a distributed messaging and streaming platform with low
latency, high performance and reliability, trillion-level capacity and flexible
scalability.
{*}Page{*}: [https://rocketmq.apache.org|https://rocketmq.apache.org/]
{*}Github{*}: [https://github.com/apache/rocketmq]
h2. Background
RocketMQ is a widely used message middleware system in the Java community,
which mainly supports Java8. As Java has evolved many new features and
improvements have been added to the language and the Java Virtual Machine
(JVM). However, RocketMQ still lacks compatibility with the latest Java
versions, preventing users from taking advantage of new features and
performance improvements. Therefore, we are seeking community support to
upgrade RocketMQ to support higher versions of Java and enable the use of new
features and JVM parameters.
h2. Task
We aim to update the RocketMQ codebase to support newer versions of Java in a
cross-compile manner. The goal is to enable RocketMQ to work with Java17, while
maintaining backward compatibility with previous versions of Java. This will
involve identifying and updating any dependencies that need to be changed to
support the new Java versions, as well as testing and verifying that the new
version of RocketMQ works correctly. With these updates, users will be able to
take advantage of the latest Java features and performance improvements. We
hope that the community can come together to support this task and make
RocketMQ a more versatile and powerful middleware system.
h2. Relevant Skills
# Java language
# Having a good understanding of the new features in higher versions of Java,
particularly LTS versions.
h3. Mentor
Yangkun Ai, PMC of Apache RocketMQ,
[aaro...@apache.org|mailto:aaro...@apache.org]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
