bossenti opened a new pull request, #2795:
URL: https://github.com/apache/streampipes/pull/2795

   <!--
     ~ Licensed to the Apache Software Foundation (ASF) under one or more
     ~ contributor license agreements.  See the NOTICE file distributed with
     ~ this work for additional information regarding copyright ownership.
     ~ The ASF licenses this file to You under the Apache License, Version 2.0
     ~ (the "License"); you may not use this file except in compliance with
     ~ the License.  You may obtain a copy of the License at
     ~
     ~    http://www.apache.org/licenses/LICENSE-2.0
     ~
     ~ Unless required by applicable law or agreed to in writing, software
     ~ distributed under the License is distributed on an "AS IS" BASIS,
     ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     ~ See the License for the specific language governing permissions and
     ~ limitations under the License.
     ~
     -->
     
     <!--
   Thanks for contributing! Here are some tips you can follow to help us 
incorporate your contribution quickly and easily:
   1. If this is your first time, please read our contributor guidelines:
       - https://streampipes.apache.org/getinvolved.html
       - https://cwiki.apache.org/confluence/display/STREAMPIPES/Getting+Started
   2. Make sure the PR title is formatted like: `[#<GitHub issue id>] PR title 
...`
   3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
`[WIP][#<GitHub issue id>] PR title ...`.
   4. Please write your PR title to summarize what this PR proposes/fixes.
   5. Link the PR to the corresponding GitHub issue (if present) in the 
`Development` section in the right menu bar. 
   6. Be sure to keep the PR description updated to reflect all changes.
   7. If possible, provide a concise example to reproduce the issue for a 
faster review.
   8. Make sure tests pass via `mvn clean install`.
   9. (Optional) If the contribution is large, please file an Apache ICLA
       - http://apache.org/licenses/icla.pdf
   -->
   
   ### Purpose
   <!--
   Please clarify what changes you are proposing and describe how those changes 
will address the issue.
   Furthermore, describe potential consequences the changes might have.
   -->
   This pull request focuses on restructuring the existing data explorer 
modules within StreamPipes. Previously, we managed two modules 
(`streampipes-data-explorer` and `streampipes-data-explorer-commons`), both 
containing StreamPipes-specific implementations as well as those tied to the 
underlying storage technology, currently InfluxDB. The aim of this effort is to 
delineate between storage-specific implementations and others, facilitating 
agnostic code writing and clearer separation.
   
   The revised module structure is as follows:
   
![image](https://github.com/apache/streampipes/assets/50115603/e5b16974-7517-4a20-b8fb-6dbf3e0ea638)
   Please note that `streampipes-data-explorer-management` is not yet 
introduced within the scope of this PR but will be included in subsequent 
updates.
   
   #### Module overview:
   
   - `streampipes-data-explorer`: encompasses all StreamPipes-specific 
implementation endeavors concerning data explorer functionalities. Several 
entities have been moved to other modules, including `streampipes-model`, 
`streampipes-data-explorer-influx` and `streampipes-data-explorer-api`.
   
   - `streampipes-data-explorer-commons`: has been removed. Content is 
distributed to other modules, including `streampipes-data-explorer`, 
`streampipes-data-explorer-influx` and `streampipes-data-explorer-api`.
   
   - `streampipes-data-explorer-api`: This module establishes the API for data 
explorer elements, consolidating important high-level interfaces. It serves as 
a centralized collection of key interfaces.
   
   - `streampipes-data-explorer-influx`: This module houses all 
InfluxDB-specific implementations necessary to fulfill data explorer storage 
functionalities utilizing an underlying instance of InfluxDB.
   
   ### Remarks
   <!--
   Is there anything left we need to pay attention on?
   Are there some references that might be important? E.g. links to Confluence, 
or discussions
   on the mailing list or GitHub.
   -->
   PR introduces (a) breaking change(s): yes
   
   PR introduces (a) deprecation(s): no
   
   #### Breaking Changes
   
   - module `streampipes-data-explorer-commons` is removed. All implementations 
are moved either to `streampipes-data-explorer` or modules introduced with this 
PR.
   - classes from `streampipes-data-explorer` have partly moved to other 
modules, including `streampipes-model`, `streampipes-data-explorer-influx` and 
`streampipes-data-explorer-api`.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to