GitHub / aws/sagemaker-python-sdk issues and pull requests
Labelled with: component: processing
#5099 - Job Name length limit
Issue -
State: closed - Opened by EnyMan 8 months ago
- 2 comments
Labels: type: bug, component: processing, component: pipelines
#4349 - Attribute error when passing kms_key to sklearn_processor.run method
Issue -
State: open - Opened by nayangirigoswamiaws almost 2 years ago
Labels: component: processing
#4116 - Document which JARs are available for PySparkProcessor by default
Issue -
State: open - Opened by j-adamczyk about 2 years ago
Labels: type: documentation, component: processing
#4082 - Add configuration of loggers for PySpark
Issue -
State: open - Opened by j-adamczyk about 2 years ago
- 1 comment
Labels: component: processing, type: logging/error reporting
#3955 - Sagemaker Pipeline DHCP error in VPC config
Issue -
State: closed - Opened by m-rajput over 2 years ago
- 7 comments
Labels: bug, component: processing
#3809 - Error message for Class PysparkProcessor--> get_run_args, when submit_py_files is not list is misleading
Issue -
State: open - Opened by JohnChe88 over 2 years ago
Labels: type: bug, component: processing, type: logging/error reporting
#3758 - sagemaker:CreateProcessingJob don't recieve empty string unlike local mode that can handle it
Issue -
State: closed - Opened by idanmoradarthas over 2 years ago
- 1 comment
Labels: bug, component: processing
#3616 - PySparkProcessor - Possibility to choose different instance types for the driver node and the worker nodes
Issue -
State: open - Opened by HarryPommier almost 3 years ago
- 1 comment
Labels: component: processing, PySpark
#3560 - ScriptProcessor does not check local_code config before uploading code to S3
Issue -
State: open - Opened by lodo1995 almost 3 years ago
- 4 comments
Labels: type: bug, component: local mode, component: processing
#3425 - Exception with ParameterString in PySparkProcessor.run() Method
Issue -
State: open - Opened by dipanjank about 3 years ago
- 8 comments
Labels: type: bug, component: processing, PySpark
#3269 - Clarify the source_dir argument in the FrameworkProcessor.run method
Issue -
State: closed - Opened by wsykala over 3 years ago
- 1 comment
Labels: type: documentation, component: processing
#3213 - More typing in the codebase, specifically for FrameworkProcessors
Issue -
State: open - Opened by MatthewCaseres over 3 years ago
Labels: type: maintenance, component: processing
#3160 - TypeError: can only concatenate str (not "list") to str
Issue -
State: closed - Opened by DanielRZapataS over 3 years ago
- 3 comments
Labels: component: processing
#3026 - Which permissions are needed to allow us to use the NetworkConfig for processing Jobs?
Issue -
State: open - Opened by JimFawkes over 3 years ago
- 1 comment
Labels: type: question, type: documentation, component: processing
#2913 - Allow storing inputs and outputs of FrameworkProcessor cross-accounts
Issue -
State: open - Opened by ksonbol almost 4 years ago
- 1 comment
Labels: type: feature request, component: processing
#2771 - New sagemaker.processing.DataWranglerProcessor class
Issue -
State: open - Opened by rodalarcon almost 4 years ago
- 1 comment
Labels: type: feature request, component: processing
#2496 - Processing job failing repeatedly with "Failed. Reason: InternalServerError: We encountered an internal error. Please try again."
Issue -
State: closed - Opened by ram-nadella over 4 years ago
- 4 comments
Labels: bug, component: processing
#2447 - Doesn't allow us to specify a directory path as an argument to submit_py_files parameter in spark_processor.run method
Issue -
State: open - Opened by koustavmukherjee over 4 years ago
- 1 comment
Labels: type: bug, contributions welcome, component: processing
#2440 - Processing Inputs limit enforcement for Local Mode
Issue -
State: closed - Opened by anirudhgangwal over 4 years ago
- 2 comments
Labels: type: feature request, UX, Local Mode, component: processing
#2117 - Possibility to add source_directory to Sagemaker.processing.ScriptProcessor
Issue -
State: open - Opened by ChaudharyKaran almost 5 years ago
- 11 comments
Labels: type: feature request, contributions welcome, component: processing
#2066 - ProcessingInput takes Dataset Definition, but does not accept raw S3 definition
Issue -
State: closed - Opened by ericangelokim almost 5 years ago
- 1 comment
Labels: UX, component: processing
#1973 - Specifiy code upload location for processing jobs
Issue -
State: open - Opened by marcelgwerder about 5 years ago
- 2 comments
Labels: type: feature request, contributions welcome, component: processing
#1869 - ScriptProcessor should expose the name of the processing job
Issue -
State: open - Opened by svpino about 5 years ago
- 4 comments
Labels: type: feature request, component: processing
#1619 - ScriptProcessor unable to handle millions of output files to be saved to S3
Issue -
State: open - Opened by maslick over 5 years ago
- 2 comments
Labels: bug, Pending information, component: processing
#1282 - ScriptProcessor does not allow us to specify S3 SSE-KMS
Issue -
State: closed - Opened by jerrygb almost 6 years ago
- 4 comments
Labels: type: feature request, component: processing
#1248 - Please add support for `requirements.txt` in ScriptProcessor similar to other "Script Mode" parts of the SageMaker Python SDK
Issue -
State: open - Opened by cfregly almost 6 years ago
- 19 comments
Labels: type: feature request, component: processing