- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13
Sync up with upstream ES main: apply project ID resolver to ScriptService. #357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
  
     Merged
                    Changes from all commits
      Commits
    
    
            Show all changes
          
          
            3 commits
          
        
        Select commit
          Hold shift + click to select a range
      
      
    File filter
Filter by extension
Conversations
          Failed to load comments.   
        
        
          
      Loading
        
  Jump to
        
          Jump to file
        
      
      
          Failed to load files.   
        
        
          
      Loading
        
  Diff view
Diff view
There are no files selected for viewing
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
        
          
          
            21 changes: 21 additions & 0 deletions
          
          21 
        
  src/main/java/co/elastic/logstash/filters/elasticintegration/util/PluginProjectResolver.java
  
  
      
      
   
        
      
      
    
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| package co.elastic.logstash.filters.elasticintegration.util; | ||
|  | ||
| import org.elasticsearch.cluster.metadata.ProjectId; | ||
| import org.elasticsearch.cluster.project.ProjectResolver; | ||
| import org.elasticsearch.core.CheckedRunnable; | ||
|  | ||
| public class PluginProjectResolver implements ProjectResolver { | ||
| @Override | ||
| public ProjectId getProjectId() { | ||
| return null; | ||
| } | ||
|  | ||
| @Override | ||
| public <E extends Exception> void executeOnProject(ProjectId projectId, CheckedRunnable<E> checkedRunnable) throws E { | ||
| if (projectId.equals(ProjectId.DEFAULT)) { | ||
| checkedRunnable.run(); | ||
| } else { | ||
| throw new IllegalArgumentException("Cannot execute on a project other than [" + ProjectId.DEFAULT + "]"); | ||
| } | ||
| } | ||
| } | 
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have to write out own project resolver? Can we use the default? https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/cluster/project/DefaultProjectResolver.java
Seems like our own one is missing some methods and i'm not sure what the implications of returning
nullwill be for a project id.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Metadata). Since this plugin doesn't include all ES module JARs, we get not class found exceptions. And when addressing@FixForMultiProjectin ES code, this will be discussion point with the ES team how LS needs to resolve project of currently running ingest pipeline. I have placed notes with my upcoming changes: https://github.com/elastic/elasticsearch/compare/main...mashhurs:elasticsearch:logstash-bridge-geoip-interfaces?expand=1nullalso breaks the plugins as we do see NPE can happen when scripts get compiled: https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/script/ScriptService.java#L596Thus, current better approach looks to me applying default project ID with minimal requirements (similar to
DefaultProjectResolverexcept default methods)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yep. Lets see what they say on that!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI: In the logstash-bridge module, there is a wrapper for Metadata and we can introduce more if we get to know how
PluginProjectResolvershould behave. This is for now a minimal change to bring the plugin into a working state.