Closed missingcharacter closed 9 months ago
@microsoft-github-policy-service agree
BTW, I tested the resulting image ghcr.io/missingcharacter/adf-shir:PR-1.6.57b4dde
myself and it works, I am able to register a node and able to create parquet
files
BTW, I tested the resulting image
ghcr.io/missingcharacter/adf-shir:PR-1.6.57b4dde
myself and it works, I am able to register a node and able to createparquet
files
Which container orchestration did you use?
Which container orchestration did you use?
@jikuja , I tested on Azure App Service on a Service Plan ith Hyper-V: true
Hi @missingcharacter, nice points to improve. It would be better to separate the changes into different PRs.
I have been re-iterating this idea on my head...
Would it be possible to do following:
SHIR/scripts/.placeholder
contrib/01-install-jvm.ps1
build.ps1
to execute .ps1
files SHIR/scripts
This would make easier to extend capabilities by adding files just before build process.
I have been re-iterating this idea on my head...
Would it be possible to do following:
- create
SHIR/scripts/.placeholder
- move code that installs JVM into
contrib/01-install-jvm.ps1
- modify
build.ps1
to execute.ps1
filesSHIR/scripts
- document this
This would make easier to extend capabilities by adding files just before build process.
lgtm
It is reasonable to keep only the basic building logic in build.ps1
for better maintainability.
@byran77 I moved GitHub Action to its own PR https://github.com/Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container/pull/19
@byran77 I've updated this PR too
thanks @missingcharacter, it looks good.
One more thing is to add some documents on the building argument INSTALL_JDK
@byran77 I added docs
Included changes: