NIO | Source des pocs NIO pour le challenge USI

do some query work with Spark SQL

You wouldn't use a ForEachWriter for that

One way to determine what section of your terrain should be culled is to use a quadtree (for a heightmap) or an octree (for a voxel map). Basically, you divide your terrain into little chunks that then get divided further accordingly. You can then test if these chunks are in your viewing frustum and cull them if necessary. This technique was already discussed in great detail:

• Efficient (and well explained) implementation of a Quadtree for 2D collision detection
• https://www.rastertek.com/tertut05.html
• https://gamedev.stackexchange.com/questions/15697/quadtree-terrain-splitting-i-dont-get-it

I saw some websites saying to use GL_DYNAMIC_DRAW instead of GL_STATIC_DRAW, but I did not understand it.

These are usage hints to OpenGL on how the data will be accessed so the implementation has the ability to apply certain optimizations on how to store/use it.

usage is a hint to the GL implementation as to how a buffer object's data store will be accessed. This enables the GL implementation to make more intelligent decisions that may significantly impact buffer object performance. (https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/glBufferData.xhtml)

Please note that these are only indications, no restrictions:

It does not, however, constrain the actual usage of the data store.

Because you will likely update your VBO's and IBO's constantly (see culling) and only want to draw them GL_DYNAMIC_DRAW would be a good choice:

The data store contents will be modified repeatedly (because of culling) and used many times. The data store contents are modified by the application and used as the source for GL drawing and image specification commands.

as I have googled that it can affect the performance of the game

Well, it will cost some performance to cull your terrain but in the end, it will likely gain performance because many vertices (triangles) can be discarded. This performance gain may grow with larger terrains.

One option is to configure that via application.properties

application.properties

The jar has to be downloaded from repos.spark-packages.org. Unfortunately this repo is not checked by pyspark when using the --packages parameter. If your machine has a running Maven installation available, the easiest way to solve the problem is to manually download the jar to your local Maven repository:

Perhaps you problem lays on @Autowired annotation on your service.

Which package is it from? It's not declared on InstallationService file, so it may be getting from another package instead of org.springframework.beans.factory.annotation, like in the other files.

You're missing on some configuration, for example generate-dll. Try with the following:

As Piotr P. Karwasz said it, I misspelled dataSourceName in context.xml and server.xml file. I feel bad that I didn't notice it.

But I still have one question : In which document should I put the realm tag ?

you have used the wrong looped variable here.

It was due to a security tool wrapped around the java executable, not due to any issue with Java itself.