I have a few questions regarding the roadmap for the AI Management module. I’ve been reviewing it for company use, and I’d like to know whether I should develop custom solutions to address these topics or wait for future releases instead.
Ok, thanks again for the reply and help!
Hello maliming,
Reopening the thread just to let you know that we had to make an adjustment to the workaround code, because we encountered another issue related to chunk storage in the Qdrant vector store implementation.
When uploading a document through AI Management Data Sources, the document is correctly chunked and embeddings are generated for all chunks. However, only the last chunk ends up being stored in Qdrant.
The issue comes from the ToPointId logic.
private static PointId ToPointId(string id)
{
if (Guid.TryParse(id, out var g)) return g;
if (id.Contains('_') && Guid.TryParse(id.Split('_', 2)[0], out var gp))
return gp;
return BitConverter.ToUInt64(
SHA256.HashData(Encoding.UTF8.GetBytes(id)), 0);
}
Chunk IDs are generated in this format: guid_0 guid_1 guid_2 ... guid_130
But the implementation extracts only the GUID part before the underscore, which means all chunks resolve to the exact same PointId.
What we did was remove that underscore special handling, so the full chunk id is preserved.
Maybe this is something that is already solved for next version as well, but maybe this helps in case it is not.
Hello maliming,
Thanks for your reply and for the workaround suggestion. We will proceed with this workaround until ABP next version is released.
We are having an issue with the current AI Management Qdrant integration implementation regarding authenticated Qdrant gRPC endpoints. The module current implementation seems to only be parsing a simple connection string (host:port or URL) and the implementation does not seem to be exposing authentication configuration.
We have been able to run the module using an authenticated Qdrant running locally, but we found no way to provide an api key (via header) which we need to access our Qdrant production endpoint.
We have checked documentation and module code. Is this something that is supported and we have not figured out how to do? Or is planned to be supported in the future?
We would like to use ABP Suite to generate code for our entities in a solution we have created using the Microservices Template. We have been adding a custom Domain Layer to all our microservices (similar to the domain layer that exists in the layered web app ABP template, but does not exist when generating microservices). The issue that we are having, is that the layer is being ignored by all our generated code. Is there a way that we can customize this process to generate the code that we need? Or is this scenario not supported?
Hello,
The document shared by the IA contains some valid and good points but i would still like the input from someone on the team.
We are working on a new solution using the ABP Microservices template, the business requierements are distinctly divided into 9 business sections, each one of them has between 3 to 8 business microservices, with an estimated total of 50 plus some infrastructure microservices. Our initial thought was to create an ABP microservice solution for each module keeping them separate and an additional solution for the infrastructure microservices, then reuse the infraestructure microservices from that additional solution such as Administration, Identity, etc across the other solutions.
However, we were wondering if it would be a better approach to use only one microservice solution and internally divide the structure into 9 distinct business sections, in order to reduce tinkering with the template code.
Is there any recommendations from ABP team to decide between this two approaches?
Thanks alper,
Copying the access token from the host filesystem to the container was the solution in this case, i had to copy the file to the project directory and make the following addition in the dockerfile:
FROM mcr.microsoft.com/dotnet/aspnet:9.0 WORKDIR /app RUN mkdir -p /root/.abp/cli COPY access-token.bin /root/.abp/cli/access-token.bin ENTRYPOINT ["dotnet", "Upm.BioforestPoC.AuditLoggingService.dll"]
I am trying out the ABP Microservices template and I am currently attempting to set up a docker compose to run the ABP microservices in a development environment in my computer. I set up Visual Studio Orcherstration Support to be able to debug the containers and i have the following docker compose with just one container (Audit Logging Service) for now.
upm.bioforestpoc.auditloggingservice:
image: ${DOCKER_REGISTRY-}upmbioforestpocauditloggingservice
build:
context: .
dockerfile: Upm.BioforestPoC.AuditLoggingService/Dockerfile
environment:
- ASPNETCORE_ENVIRONMENT=Development
ports:
- "44361:44361"
Docker file is very simple for now
FROM mcr.microsoft.com/dotnet/aspnet:9.0
WORKDIR /app
ENTRYPOINT ["dotnet", "Upm.BioforestPoC.AuditLoggingService.dll"]
When i run the docker compose using Visual Studio, my container is crashing because of a failed licensing check
[20:53:08 ERR] ABP-LIC-ERROR - License check failed for 'Volo.Saas.Domain-v9.1.0.0'.
You need to log in using the command abp login <username>.
For more information, contact to license@abp.io.
I am logged on the ABP CLI in my host computer, but i am not sure how to "transfer" the license to the container i am debugging. I have tried using other ASPNETCORE_ENVIRONMENT values instead of Development such as Production or Local because it is what we do with our other ABP applications running in production in containers, but the error persists.
I would like to be able to debug the services running in containers, any help would be appreciated!
